T08 · Insecure Dependencies
- Location
scripts/bootstrap_env.py:54- Finding
Unpinned Dependencies and Mutable Model Artifacts Create a Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent arXiv digest skill, but it needs Review because it combines scheduled automation, repository write behavior, unpinned installs, plaintext arXiv queries, and optional third-party AI data sharing.
Install only if you are comfortable with scheduled local or optional GitHub automation, network queries to arXiv, and optional OpenAI processing. Prefer offline Argos translation, avoid TRANSLATE_PROVIDER=auto/openai for sensitive work, review the GitHub Actions workflow before enabling it, and pin dependencies/models if using this in a controlled environment.
scripts/bootstrap_env.py:54Unpinned Dependencies and Mutable Model Artifacts Create a Supply-Chain Risk
scripts/run_digest.py:42User Research Interests Are Transmitted to arXiv over Plaintext HTTP
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: agent-daily-paper
description: 支持用户按一个或多个研究领域订阅 arXiv 最新论文,按重要性排序并以中英双语卡片形式推送(英文标题/中文标题/英文摘要/中文摘要/arXiv 链接)。支持每领域独立数量上限(5-20)、关键词高亮、NEW/UPDATED 版本标识、Markdown 存档,以及定时推送与即时推送双路径。首次使用时先完成订阅配置;领域可由 Agent 画像 JSON 自动补全英文名、关键词与会议列表。
---
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
---
name: agent-daily-paper
description: 支持用户按一个或多个研究领域订阅 arXiv 最新论文,按重要性排序并以中英双语卡片形式推送(英文标题/中文标题/英文摘要/中文摘要/arXiv 链接)。支持每领域独立数量上限(5-20)、关键词高亮、NEW/UPDATED 版本标识、Markdown 存档,以及定时推送与即时推送双路径。首次使用时先完成订阅配置;领域可由 Agent 画像 JSON 自动补全英文名、关键词与会议列表。
---
Referenced artifact was not completely inspected
这些规则属于 Agent 行为规范,维护在 `SKILL.md` 中,不应在 `run_digest.py` 里硬编码风格替换规则。
The README recommends an OpenAI-based translation provider via OPENAI_API_KEY but does not clearly warn that paper titles, abstracts, or possibly extracted PDF text may be sent to an external third-party service. In a research workflow, this can expose unpublished, sensitive, or proprietary document content to an external provider without informed consent.
The README explicitly describes scheduled execution, local file writes, and in the GitHub Actions path automatic commits of output and state, but it does not prominently warn users that installing or enabling the skill can create persistent local changes and, in remote setups, push updates back to a repository. In an agent-installation context, that omission can lead users to authorize automation without understanding that the skill may continuously modify files or generate repository activity over time.
The README says the agent 'must' use a fixed prompt framework for '中文结构化输出' and later requires '请使用...中文输出'. This is a natural-language locale constraint that forces a specific language rather than offering the user a choice, and no justification or opt-in is provided in the surrounding text.
The output specification requires the paper interpretation to be a Chinese long-form passage, and the later prompt template also mandates Chinese structured output. This is a language policy constraint presented as mandatory behavior, with no indication that the user can choose another language or opt in.
The single-paper interpretation section states the agent must use a fixed prompt framework and explicitly requires structured Chinese output, culminating in a requirement for at least 1000 Chinese characters. This is a natural-language locale restriction that applies regardless of user preference.
Suspicious Unicode normalization or mixed-script content
The setting "insight_lang": "zh" hard-codes a specific output language for this subscription. Under the policy, forcing a language or locale without user choice or a clearly documented region-specific justification is a natural-language policy violation.
This subscription likewise sets "insight_lang": "zh", which imposes a specific language choice in configuration. The file provides no indication of user choice, opt-in, or a justified locale restriction.
The configuration sets "insight_lang": "zh", which hard-codes the output language to Chinese. Under the policy rules, forcing a specific language without explicit user opt-in or a documented region-specific justification is a natural-language policy concern.
The natural-language string in the configuration is written only in Chinese, which imposes a specific language on users without any visible opt-in or alternative locale handling. This matches the policy category for language or locale constraints that are not optional or justified.
This manifest sets "insight_lang": "zh", which imposes a specific output language in configuration rather than offering a user-selectable locale. The file contains no nearby indication that the language is optional, user-chosen, or justified as a region-specific tool, so it appears to violate the language/locale policy.
The string assigned to setup_message is user-facing natural language and is written only in Chinese. For a cross-language bootstrap script, this forces a specific language without user opt-in, which matches the language/locale policy violation criteria.
This code file contains a natural-language status message in Chinese, while the rest of the script is otherwise English-oriented, and there is no indication that the skill is intentionally restricted to Chinese-speaking users. Under the policy rule, forcing a specific language without user opt-in or documented justification is a locale-policy violation.
When --use-openai-profile is enabled, the script sends the user-supplied field_name to https://api.openai.com/v1/responses. This code path has no print/log statement, confirmation prompt, or inline warning near the transmission, so users running the script may not realize their input is being sent to an external service.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
}
req = Request(
"https://api.openai.com/v1/responses",
data=json.dumps(body).encode("utf-8"),
headers={"Content-Type": "application/json", "Authorization": f"Bearer {api_key}"},
method="POST",
The CLI sets --insight-lang default to zh, which imposes a specific output language unless the user overrides it manually. This is a natural-language policy concern because the skill defaults to one language rather than obtaining user language preference or making the choice neutral by default.
This code sends paper titles and abstracts to the OpenAI Responses API whenever the provider is set to openai/auto and credentials are present, but there is no in-code consent gate, disclosure, redaction step, or policy control over outbound data sharing. Even if arXiv metadata is often public, the finding is still valid because the skill transmits user-selected content to a third party and the surrounding config may include nonpublic or policy-sensitive material in other deployments.
This is a concrete external transmission sink to api.openai.com carrying the translation payload and authorization header. In the context of this skill, the danger is not the HTTPS destination itself but that outbound sharing of paper content occurs without an explicit trust boundary control, user notice, or minimization of transmitted data.
}
req = Request(
"https://api.openai.com/v1/responses",
data=json.dumps(body).encode("utf-8"),
headers={"Content-Type": "application/json", "Authorization": f"Bearer {api_key}"},
method="POST",
This helper transmits arbitrary English text to the OpenAI API for translation into Chinese, and that text can include extracted PDF content, summaries, or other assembled content beyond just public metadata. Because the function accepts free-form text and is used in the insight-generation pipeline, the privacy and data-governance risk is broader than the title/abstract case.
This second external transmission sink sends arbitrary text for translation to OpenAI over the network. In this skill's context it is more sensitive because upstream callers may provide PDF-extracted or synthesized content, increasing the chance of sending larger or more sensitive text to a third party without explicit approval.
],
}
req = Request(
"https://api.openai.com/v1/responses",
data=json.dumps(body).encode("utf-8"),
headers={"Content-Type": "application/json", "Authorization": f"Bearer {api_key}"},
method="POST",
This JSON profile uses a Chinese field name as the primary identifier (数据库优化器) while the file provides no indication that users can choose their preferred language or locale. That can create a language/locale policy issue because the skill configuration implicitly privileges one language without documented opt-in or justification.
summarize_paper_insight defaults insight_lang to "zh", which imposes a specific output language absent any explicit opt-in at this point in the code. The policy allows locale constraints when user choice is explicit, but this default can cause forced language behavior.