T08 · Insecure Dependencies
- Location
SKILL.md:168- Finding
Unpinned Global npm Package Installation Creates Supply-Chain Risk
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill has a coherent bookmark-monitoring purpose, but it asks users to run unaudited install/daemon commands and store sensitive session/API credentials with inconsistent privacy claims.
Review this before installing. Do not place real social session tokens, AI keys, bot tokens, or Slack webhooks into this skill unless you trust the publisher and can verify the missing implementation. Avoid global npm installs from these instructions without pinned package provenance, and treat the PM2 daemon as persistent software that may keep processing bookmark content and sending data to external services.
SKILL.md:168Unpinned Global npm Package Installation Creates Supply-Chain Risk
SKILL.md:230API Keys and Session Credentials Are Stored in Plaintext Configuration Files
SKILL.md:168Missing Implementation Prevents Verification of Executable and Privacy Claims
The skill explicitly instructs users to provision and store high-value secrets including social auth tokens, AI API keys, and notification credentials. In an agent-skill context with read/exec/write capabilities, encouraging credential placement in accessible local files increases the blast radius of any compromise or accidental disclosure.
config.json 的 aiApiKey 字段配置 AI 分析模型 API Key.# .env 环境变量示例
AUTH_TOKEN=your_social_auth_token
CT0=your_social_ct0_token
AI_API_KEY=your_ai_api_key
The invocation guidance is very broad and encourages use whenever AI/model invocation or agent orchestration is needed, without clear limits, trust boundaries, or consent requirements. In the context of a skill that can execute commands, run background monitoring, and handle credentials, overly broad triggers increase the chance of unsafe or unintended activation.
The skill describes daemonized background monitoring, PM2 management, notifications, credential setup, and external AI/API use without prominent up-front warnings or consent gating. Because these behaviors persist, access external services, and may process sensitive content, the lack of early warning materially increases user risk.
The document states 'no telemetry, no callback/upload' while also describing transmission of article content to external LLM APIs and use of external notification services like Telegram and Slack. This contradiction is security-relevant because users may believe data never leaves the host when in fact content is sent to third parties.
The skill claims it does not store personal credentials or sensitive information, yet elsewhere explicitly instructs users to place tokens and API keys in local .env and config files. This is a materially misleading privacy/security statement that can cause users to underestimate the sensitivity of the local files and mishandle secrets.
No suspicious patterns detected.