T08 · Insecure Dependencies
- Location
SKILL.md:127- Finding
Unpinned npm Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears intended for Chinese official-document formatting, but its install and post-processing steps create avoidable supply-chain and document data-loss risks.
Review before installing. Run it only on copies of documents, preferably in an isolated workspace, and avoid following the unpinned npm install step unless you pin and review the dependency. The skill does not show exfiltration or hidden persistence, but its current scripts can corrupt or delete local document files during failures.
SKILL.md:127Unpinned npm Dependency Installation
scripts/fix_fonts.py:11Predictable Temporary Directory Is Recursively Deleted
scripts/fix_fonts.py:294Source DOCX Is Deleted Before Replacement Is Safely Committed
Referenced artifact was not completely inspected
2. 直接复用 `scripts/generate_gongwen_docx.js`(解析 markdown -> 公文,已固化全部规则):
Referenced artifact was not completely inspected
2. 直接复用 `scripts/generate_gongwen_docx.js`(解析 markdown -> 公文,已固化全部规则):
Referenced artifact was not completely inspected
2. 直接复用 `scripts/generate_gongwen_docx.js`(解析 markdown -> 公文,已固化全部规则):
The skill instructs the agent to read user-provided Markdown, text, and old docx inputs and references local scripts and files, which implies file-read capability, but it does not declare any explicit tool scope or allowed-tools boundary. Missing scope declarations increase the risk of over-broad file access or accidental use of file-reading in contexts beyond the intended document-conversion workflow.
The activation criteria are very broad and overlap with ordinary document-editing and formatting requests, so the skill may trigger in many benign writing scenarios where users did not intend this specialized workflow. Over-broad activation can route sensitive documents into a pipeline that reads files, applies local scripts, and transforms content under assumptions the user did not explicitly approve.
This workflow mandates a specific language/locale context throughout the skill content and does not indicate that users may choose another language or opt in to Chinese-only behavior. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy violation unless the constraint is explicitly documented and justified as region-specific.
The script removes the original input .docx and recreates it in place, so any interruption during repackaging (parse error, disk full, permission issue, crash) can permanently destroy the only copy. In this skill context, users are likely processing important official documents, which increases the practical risk of irreversible data loss even though this is not an exploit-oriented bug.
The file's natural-language description and CLI usage are written entirely in Chinese and define the skill's purpose as generating documents conforming to Chinese government document standards. There is no indication that users can opt into this locale or choose another language, which can be a language/locale policy violation under the stated rules.
No suspicious patterns detected.