T08 · Insecure Dependencies
- Location
SKILL.md:89- Finding
Unverified Third-Party Executable Dependency
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to be a legitimate website auditing workflow, but it needs review because it runs an unverified external CLI, encourages live crawling, can edit local projects, and documents piping website-derived reports directly into an AI agent.
Review this skill before installing. Use it only with websites you own or are authorized to test, verify the squirrel CLI source and version before running it, avoid piping raw audit output directly into an agent without treating it as untrusted data, and require explicit approval before config overwrites, self-updates, skill updates, subagents, or project edits.
SKILL.md:89Unverified Third-Party Executable Dependency
references/OUTPUT-FORMAT.md:195Untrusted Website-Derived Report Content Piped Directly into an AI Agent
The documented use of squirrel init --force can overwrite an existing configuration file, which is a form of self-modification or destructive local state change. While not inherently malicious, it can erase project-specific settings or disrupt an existing audit setup if followed blindly by an agent.
squirrel init -n my-project
# overwrite existing config
squirrel init -n my-project --force
The skill is presented as a website auditing/reporting tool, but these instructions expand its behavior into modifying project files and implementing fixes. That broadens the trust boundary from read/report operations to write operations, increasing the chance of unintended code or content changes without clear user authorization.
The skill encourages auditing live websites and performing deeper scans that may impact the target, but it does not require confirming authorization, ownership, or permission to scan. In practice, this could prompt agents to crawl third-party sites in ways that raise legal, privacy, or operational concerns.
The workflow tells the agent to apply fixes and verify builds, which exceeds a reporting-oriented skill and introduces write/build execution behavior. This can lead to unauthorized repository modifications or execution of project checks in environments where the user only requested analysis.
This section operationalizes an iterative remediation loop: fixing files, re-auditing, and continuing until a score target is reached. That turns an analysis skill into an autonomous code/content modification workflow, which is risky because optimization for a scanner score may cause incorrect, low-quality, or user-unapproved changes.
No suspicious patterns detected.