← Back to Scanner

omnisync Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

omnisync is an AI agent skill, created by ErkRodCS and published at ErkRodCS/OmniSync_Standard. ClawSecure audited omnisync across 10 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 91/100 (Safe). The 4 findings concentrate in Policy Violation, Obfuscation and Verification, including File 'requirements.txt' extension (.txt) suggests one format but Magika... and __pycache__ directory found at __pycache__/ containing 1 bytecode.... None were rated high or critical severity.

Is omnisync safe?

ClawSecure audited omnisync and assigned a security score of 91/100 (Safe), identifying 4 findings across Policy Violation and Obfuscation. Review the findings below before installing.

What did ClawSecure find in omnisync?

ClawSecure identified 4 findings in omnisync, concentrated in Policy Violation, Obfuscation and Verification. The most severe include File 'requirements.txt' extension (.txt) suggests one format but Magika... and __pycache__ directory found at __pycache__/ containing 1 bytecode....

How was omnisync audited?

ClawSecure ran omnisync through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 10 files from ErkRodCS/OmniSync_Standard.

What does a score of 91 mean?

ClawSecure assigned omnisync a security score of 91/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 4 findings detected are lower-severity. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for omnisync

ClawSecure detected 4 security findings in omnisync, spanning Policy Violation, Obfuscation and Verification.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for omnisync

Resolve policy violations
omnisync trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Review obfuscated or hidden code
omnisync contains obfuscated or hidden content that resists review. Inspect encoded, minified or hidden files to confirm they are not concealing unexpected behavior before installing.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.
Add a config.json permissions manifest
A config.json file declares what permissions an agent component needs: file system access, network requests, shell execution and more. Without it, users have no visibility into what the component can do before installing. Adding a permissions manifest is the single most impactful security improvement for any AI agent skill.

Related Security Research

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolWhy Generic Scanners Fail at AI Agent Security

Related AI Agent Security Audits

sonoscliScore 95/100f968405e77f5edd5Score 95/100wacliScore 95/100a6fe8825e22682daScore 95/100cbc3dac9d0cccf41Score 95/100

Scanned on June 23, 2026. omnisync is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan