T08 · Insecure Dependencies
- Location
scripts/install-deps.sh:26- Finding
Unpinned Python dependencies are installed from the active package index
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This looks like a legitimate Chinese bid-document generator, but it warrants review because it handles sensitive procurement files and includes under-scoped guidance that may affect confidentiality, supply chain safety, and document provenance.
Install only in a controlled workspace, review generated bid content before submission, avoid uploading tender documents to public OCR services unless your organization approves it, use pinned dependencies from trusted sources, and do not install fonts downloaded from unverified search results. Treat the automatic DOCX metadata rewrite and AI-trace removal as provenance-affecting behavior.
scripts/install-deps.sh:26Unpinned Python dependencies are installed from the active package index
scripts/check-font.sh:52Font installation guidance directs users to an unspecified Internet source without integrity verification
~/Library/Fonts/scripts/parse_bid_files.py:109Scanned bid documents may be disclosed to a third-party online OCR service
The changelog explicitly states that convert_to_word.py rewrites Word metadata such as creator/description and timestamps, but this behavior is not surfaced as a security-relevant capability in the main description. Undisclosed metadata modification can hinder provenance tracking, confuse audit trails, and conceal document origin in procurement workflows where authenticity matters.
The changelog explicitly states that convert_to_word.py rewrites Word metadata such as creator/description and timestamps, but this behavior is not surfaced as a security-relevant capability in the main description. Undisclosed metadata modification can hinder provenance tracking, confuse audit trails, and conceal document origin in procurement workflows where authenticity matters.
The changelog explicitly states that convert_to_word.py rewrites Word metadata such as creator/description and timestamps, but this behavior is not surfaced as a security-relevant capability in the main description. Undisclosed metadata modification can hinder provenance tracking, confuse audit trails, and conceal document origin in procurement workflows where authenticity matters.
The changelog explicitly states that convert_to_word.py rewrites Word metadata such as creator/description and timestamps, but this behavior is not surfaced as a security-relevant capability in the main description. Undisclosed metadata modification can hinder provenance tracking, confuse audit trails, and conceal document origin in procurement workflows where authenticity matters.
The changelog explicitly states that convert_to_word.py rewrites Word metadata such as creator/description and timestamps, but this behavior is not surfaced as a security-relevant capability in the main description. Undisclosed metadata modification can hinder provenance tracking, confuse audit trails, and conceal document origin in procurement workflows where authenticity matters.
The document declares Chinese as the page language with lang="zh-CN", and the entire installation and usage flow is written only in Chinese without offering an alternate language or stating that the skill is intentionally limited to Chinese-speaking users. This can violate language/locale policy when a skill imposes a specific language by default rather than by user opt-in or documented regional scope.
The skill declares installation steps and an output path indicating local file reads/writes, but it does not declare any explicit tool scope or permissions boundaries. That creates an authorization gap: an agent may infer broader filesystem access than users expect, increasing the risk of unintended access to local documents during bid-processing workflows.
该技能具备 Read/Write/Edit 能力,但说明中未清楚提醒其会直接修改用户文本,也未要求在覆盖前确认。对于投标、技术文档等高价值内容,这种静默编辑可能导致措辞、证据强度或格式要求被改变,进而影响合规性、准确性和业务结果。
该技能的触发条件“编辑或审阅文本,去除 AI 写作痕迹”过于宽泛,容易与普通润色、审校、改写等常见请求重叠,导致在用户并未明确要求时被自动调用。一旦触发,它会按预设规则系统性重写内容,可能改变原文语气、事实表述或合规措辞,带来非预期内容篡改风险。
Nearly all comments and terminal output are written only in Chinese, which imposes a specific language on users without opt-in or an alternative locale. This matches the language/locale policy violation criteria because the skill does not provide any user choice or clearly document a justified region-specific restriction.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
echo "🐧 Linux 安装方法:"
echo ""
echo " # 创建用户字体目录"
echo " mkdir -p ~/.fonts"
echo " cp SimSun.ttf ~/.fonts/"
echo " fc-cache -fv"
;;
The function and its docstring explicitly count only Chinese characters and ignore punctuation, English, and numbers, making the skill inherently language-specific. Elsewhere the script also labels its purpose as chapter word counting generally, but it does not offer a language choice or state that it is restricted to Chinese-language documents, which conflicts with the policy against forcing a specific language without opt-in.
The module docstring, usage text, and user-facing messages are all written exclusively in Chinese, which constitutes a language-specific constraint in the skill's natural-language interface. The file does not offer an opt-in language choice or explain that the tool is intentionally limited to a Chinese-only environment.
The module docstring, usage instructions, warnings, and returned status strings are all written in Chinese, which imposes a specific language on users. The file does not provide an opt-in language choice or explain that the skill is intentionally limited to a Chinese-speaking or region-specific context.
This code file performs a user-facing file metadata disclosure via ls -lh "$FONT_PATH", which reveals the exact path, size, permissions, and timestamps of a file in the user's home directory. Although it prints the result, the script header and usage text do not warn that local filesystem details will be displayed, so the disclosure lacks advance notice.
The script's comments and user-visible echo messages are written in Chinese throughout, which effectively imposes a specific language on users. The file does not offer an opt-in choice of language or explain that the skill is intentionally limited to a Chinese-speaking or region-specific context.
This code file contains natural-language docstrings and CLI output entirely in Chinese, including the script description and usage text. Under the policy, forcing a specific language without user opt-in or a documented justification is a natural-language policy violation.
No suspicious patterns detected.