T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill appears aligned with publishing to pub.blue, but it should be reviewed because it uses mutable npm execution and persistent API-key/daemon behavior with limited safety guidance.
Install only if you trust the pub.blue npm package and service. Prefer a pinned reviewed CLI version, avoid putting real API keys directly in command history or shared transcripts, use a restricted config directory when possible, do not publish sensitive content accidentally, confirm delete behavior before relying on recovery, and stop the daemon when live sessions are no longer needed.
SKILL.md:19Unpinned Global Installation of a Third-Party npm Package
The skill allowlists and documents execution via npx pubblue:* without pinning a specific package version, which can cause the agent to fetch and run whatever version is currently published. In an automated agent context, this increases supply-chain risk and reduces reproducibility, especially because the skill itself also says to install @latest, reinforcing mutable execution targets.
The setup section instructs users to pass an API key on the command line or via stdin and discloses the default credential storage path, but provides no warning about secret handling, file permissions, shell history, or log exposure. In an agent environment, such omissions can lead to accidental credential leakage or insecure persistence of long-lived tokens.
The skill description lists pubblue delete <slug> among core commands but does not mention that it removes a pub or whether the action is reversible. For markdown files, destructive operations that can affect user data should include a clear warning so users understand the impact before using them.
No suspicious patterns detected.