T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Unnecessary Unpinned Dependencies Create Supply-Chain Exposure
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s core code is a local Mermaid diagram generator, but its install instructions pull unnecessary unpinned packages and its activation scope is broader than its medical diagram purpose.
Review before installing. The diagram generator itself appears narrow and local, but avoid running the documented pip install step as written; remove the unnecessary dependencies or pin and verify any packages first. Treat Mermaid output generated from untrusted text as untrusted and render it only with a restrictive Mermaid security configuration.
requirements.txt:1Unnecessary Unpinned Dependencies Create Supply-Chain Exposure
scripts/main.py:38User-Controlled Mermaid Syntax Injection Through Ineffective Label Escaping
The activation guidance is broader than the stated purpose of generating medical/pathophysiology Mermaid diagrams, including generic data-analysis use. Overbroad routing criteria can cause the wrong skill to be invoked on inputs it is not designed to handle, which increases the risk of unsafe assumptions, misuse of scripts, or inappropriate processing of files and user data.
The trigger text broadens activation from a narrowly defined pathophysiology flowchart skill to generic data analysis tasks requiring assumptions, bounded scope, and reproducible output. That can cause the agent to route unrelated requests into this skill, increasing the chance of out-of-scope execution, misleading outputs, and bypass of more appropriate safety or domain-specific handling. The audit evidence also supports this concern because the stress case recorded scope-boundary and guidance failures.
The risk assessment states 'Network Access | No external API calls' even though this file is only documentation and does not include the referenced implementation in scripts/main.py. Because the document makes a concrete behavioral claim about runtime behavior that is not demonstrated here, the documentation overstates what is established by the artifact being reviewed.
The file claims the skill reads input files, writes output files, validates paths against traversal, and restricts output to the workspace, yet this markdown file contains no executable logic implementing those controls. That creates an intent-versus-evidence gap where the documentation presents safeguards as if they are active behavior.
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
dataclasses
enum
Dependencies lack version pinning, allowing potential malicious package updates. Consider pinning versions.
dataclasses
enum
No suspicious patterns detected.