T08 · Insecure Dependencies
- Location
claw.json:18- Finding
Unpinned External Dependencies Execute Security-Critical Code
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This security-suite skill is not clearly malicious, but it needs review because it can modify user files, relies on unpinned external scanner/fixer code, and may overstate compliance certification results.
Install only if you are comfortable running unpinned third-party scanner/fixer code on the target skill directory. Use scan and dry-run first, review diffs before applying fixes, avoid relying on generated certificates as real SOC 2, HIPAA, PCI-DSS, or GDPR compliance proof, and avoid writing reports over important existing files.
claw.json:18Unpinned External Dependencies Execute Security-Critical Code
scripts/suite.py:137Compliance Certificates Can Be Issued Without Affirmative Control Validation
The documentation claims a complete security and compliance suite, but the described behavior extends beyond the declared description and references supporting components not present in this file. Security tooling that overstates coverage or certification capability can create false assurance, causing users to trust scans, fixes, or compliance outputs that may be incomplete or unsupported.
The skill advertises capabilities that read and modify user files, but it does not declare any explicit tool scope such as permissions or allowed-tools. That makes the operational boundary unclear and can lead to over-broad execution in environments that rely on manifest-declared permissions for policy enforcement and user trust.
The skill describes auto-fix behavior that rewrites files and can apply all fixes automatically, but it does not prominently warn users that their files may be modified. In a security tool, silent or insufficiently disclosed mutation of source trees can cause data loss, unsafe changes, or unwanted bulk edits to sensitive code and configuration.
The quick-start examples prominently include automatic remediation commands such as '--auto' without any adjacent caution about backups, destructive edits, or review before applying changes. Users commonly copy-paste quick-start commands, so unsafe examples materially increase the chance of accidental modification of production or sensitive files.
The module and CLI present framework-specific reporting and certification, implying certificate metadata should correspond to the selected framework. However, generate_certificate_id hardcodes a SOC2 prefix for every certificate, which contradicts the framework-specific certification behavior implemented elsewhere.
The fix command invokes scan-and-fix and apply_fixes, which are file-modifying operations, but this file provides only terse command help and progress messages after execution starts. There is no clear user-facing warning in code comments, docstrings, or prompts here that running fix/--auto will change files, which is a safety-relevant operation for a general security suite.
The manifest description enumerates scanner, fixer, and compliance reports for SOC2, HIPAA, and PCI-DSS. The code expands that advertised scope by defining a GDPR framework and exposing it through both the report and certify CLI commands, so the implemented behavior does not match the stated description.
The code writes report content to a user-supplied path using Path.write_text, and a similar write occurs for certificates. Although writing output files is part of the command purpose, this file does not disclose overwrite behavior or emit a confirmation when saving to an existing path.
The certify command saves generated certificate text to a caller-provided path with Path.write_text. This is a file-write operation with no explicit overwrite warning or confirmation in this file, which may surprise users if the target file already exists.