T08 · Insecure Dependencies
- Location
SKILL.md:123- Finding
Unpinned Package Retrieval and Immediate Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real Mermaid diagram helper, but its setup and troubleshooting guidance includes risky unpinned package execution and weakened browser security settings.
Review before installing. Prefer installing a pinned, reviewed Mermaid CLI version in a project with a lockfile, avoid one-shot npx/dlx/bunx execution for sensitive work, and do not disable the Chromium sandbox unless rendering only trusted diagrams inside a constrained environment.
SKILL.md:123Unpinned Package Retrieval and Immediate Execution
SKILL.md:265Chromium Sandbox Disabled During Mermaid Rendering
The trigger conditions are extremely broad, including generic phrases like '画个图' and instructing proactive use even when the user did not request Mermaid explicitly. Overbroad activation can cause the agent to invoke this skill in unrelated contexts, leading to unintended file creation and shell command execution (mmdc, file writes, open commands) on user systems.
The natural-language description and instructions are entirely in Chinese, and the skill does not indicate any user language choice or opt-in behavior. This can violate language or locale policy when the broader environment or user has not explicitly requested Chinese-only interaction.
The skill instructs use of npx -p @mermaid-js/mermaid-cli without pinning a specific version, which allows execution of whatever package version is current at runtime. This creates a supply-chain risk: a malicious or compromised upstream release could be fetched and executed on the user's machine without review, especially because the command is presented as a recommended fallback.
The unpinned npx @mermaid-js/mermaid-cli guidance similarly permits downloading and executing the latest package version at invocation time. In a skill that encourages command execution, this increases exposure to dependency hijacking, malicious releases, or breaking changes that can lead to unsafe or unexpected code execution.
No suspicious patterns detected.