T08 · Insecure Dependencies
- Location
scripts/suggest.py:16- Finding
Untrusted External Module Import Enables Arbitrary Code Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This refactoring skill is not clearly malicious, but it can modify projects more broadly and less safely than it claims.
Review carefully before installing. Use only on version-controlled test projects, run with --dry-run first, avoid --no-backup, do not pass untrusted backup IDs to undo, and be aware that advertised refactorings and safety guarantees do not match the shipped implementation.
scripts/suggest.py:16Untrusted External Module Import Enables Arbitrary Code Execution
scripts/rename.py:258Unvalidated Backup Identifier Allows Directory Traversal During Restore
scripts/rename.py:231Incorrect AST Offsets Can Cause Destructive Source-Code Modification
scripts/main.py:157Documented Preview-by-Default Safety Control Is Not Implemented
If the underlying implementation performs rename operations via text replacement rather than AST-aware symbol refactoring, the claim of 'safe' refactoring is misleading and can cause unintended edits in comments, strings, or unrelated identifiers. In a code-modifying skill, overstated safety features materially raise the chance of integrity-impacting changes because users may trust it to make bulk edits automatically.
If the underlying implementation performs rename operations via text replacement rather than AST-aware symbol refactoring, the claim of 'safe' refactoring is misleading and can cause unintended edits in comments, strings, or unrelated identifiers. In a code-modifying skill, overstated safety features materially raise the chance of integrity-impacting changes because users may trust it to make bulk edits automatically.
If the underlying implementation performs rename operations via text replacement rather than AST-aware symbol refactoring, the claim of 'safe' refactoring is misleading and can cause unintended edits in comments, strings, or unrelated identifiers. In a code-modifying skill, overstated safety features materially raise the chance of integrity-impacting changes because users may trust it to make bulk edits automatically.
Without declared permissions the skill's intent is opaque and cannot be validated.
The skill description and feature documentation switch to Chinese and present the usage instructions in that language without stating that another language is available. This creates a locale/language constraint in the skill's natural-language interface without user opt-in, which matches the policy-violation category.
The roadmap explicitly shows extract method, inline variable, move code, and refactoring suggestions as unchecked, which indicates they are not yet implemented. This directly conflicts with earlier sections that describe these operations as supported features with concrete usage examples, creating active intent/documentation divergence within the skill file.
No suspicious patterns detected.