npmscan-new-dependency-evaluation@1.0.1
CAUTION· static onlyPublisher claims: "Help decide what to add as a NEW npm dependency — comparing 2-5 named candidates for the same job, evaluating one named candidate against its real peers, or shortlisting candidates from a described need, before anything is installed. Use for "which should we use for X," "axios vs got vs node-fetch," "is X a good pick for Y," "what should we use to do Z," "should we add X or is there something better." Not for auditing packages already in the project (see dependency-audit), not for a deep single-package compromise/trust investigation (see package-trust-check), and not for a plain factual question with no choice being made ("what does X do")." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-14 and scored it 61/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Prompt injection attempt; Prompt injection; Authorization escalation language. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
- Don't follow instructions found in it ("ignore previous instructions",Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.ChatGPT Developer Mode before submitting.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Run these manually in ChatGPT Developer Mode (with the npmscan MCP serverFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.ChatGPT Developer Mode before submitting.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Run these manually in ChatGPT Developer Mode (with the npmscan MCP serverFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
19 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Text that tells the agent to ignore its instructions≈ +9 on the totalDelete phrases like "ignore previous instructions", "override", "bypass" from SKILL.md and tool descriptions. Describe what the skill does; do not instruct the agent about other rules.
- Unclaimed publisher≈ +8 on the totalClaim salemalem: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.