T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Third-Party Package and Model Artifacts
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill broadly indexes local memory files and mostly matches its purpose, but its file scoping and dependency integrity controls are too loose for automatic installation.
Review before installing. Use it only in a dedicated, low-privilege workspace; pin Python dependencies and the model revision; validate manifest paths against a specific memory directory; and do not enable recurring maintenance until the file scope is constrained and understood.
SKILL.md:24Unpinned Third-Party Package and Model Artifacts
scripts/build_index_bge.py:22Manifest Paths Permit Reads Outside the Intended Memory Directory
The manifest description says to trigger on phrases like "long-term memory," "agent memory," and "memory management" without defining clear boundaries, exclusions, or a constrained invocation context. These phrases are broad enough to match ordinary discussion about AI memory or knowledge bases, which could cause unintended activation.
The document uses Chinese headings and instructions throughout, which imposes a specific language choice without indicating user opt-in or that the skill is intentionally region-specific. Under the policy rule, a forced language/locale is a natural-language policy concern unless the file offers a choice or documents a justified locale constraint.
The file's operative instructions and field labels are presented exclusively in Chinese, with no indication that users may choose another language or locale. This can violate language/locale policy when a skill implicitly requires one language without documenting opt-in or regional scope.
subprocess module calls execute external commands. Without careful input validation, this enables command injection.
def has_palace_changes_since_last_commit() -> bool:
"""方案 A: git diff 门。检查 palace/ 是否有未提交变更。"""
result = subprocess.run(
["git", "diff", "--name-only", "HEAD", "--", "memory/palace/"],
capture_output=True, text=True, cwd=ROOT
)
This file contains natural-language descriptions and runtime messages that force a specific language/locale for operators. The policy allows fixed locale only when user opt-in or a justified region-specific constraint is documented, which is not present here.
This code file contains user-facing natural-language instructions exclusively in Chinese in the module docstring and command examples. Under the policy, forcing a specific language without offering a choice or documenting a justified locale constraint is a natural-language policy violation.
The headings on these lines use Chinese-only labels for date and status, which imposes a specific language in the skill file without any user opt-in or justification that the skill is intended for a Chinese-language environment. This matches the policy category for language or locale constraints expressed in natural language.
This Python file executes a git subprocess via subprocess.run, which is one of the safety-relevant operations covered by the warning rule for code files. Although the script logs the diff results afterward, there is no prior disclosure, prompt, or explicit explanatory warning near the execution site that the skill will invoke an external command.
The script’s human-facing comments and console messages are entirely in Chinese, including status output and usage guidance. This imposes a specific language on operators without offering a language choice or documenting that the skill is intentionally region-specific, which matches the locale-policy concern for natural-language content.