opencode-skills-collection@4.0.56
OpenSSF/OSV Malicious Advisory
imported 8h ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18193 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
This is a first-party OpenCode extension that mutates an agent control surface at runtime, warranting a warning. Static inspection found no install hook, self-dependency, credential theft, or package-runtime network behavior that would justify blocking.
Independent scan evidence
public snapshot- The OpenCode plugin runs on startup and populates the user's OpenCode skills directory.
- It recursively deletes stale category-pointer directories and overwrites its managed pointer files.
- It copies the bundled skill collection into a user-level OpenCode vault, making its instructions available to the agent.
- package.json has only a prepublish hook, so registry installation does not run package code.
- The plugin runtime contains no outbound network request or credential collection.
- The flagged Apify, Hugging Face, and Playwright utilities are separate examples invoked explicitly; their network, token, and install actions are not reached by the plugin.
Source & flagged code
10 flagged · loading sourcePackage contains a high-severity secret pattern.
bundled-skills/developer-signup-flow/SKILL.mdView on unpkg · L165Stripe test secret key in bundled-skills/developer-signup-flow/SKILL.md
bundled-skills/developer-signup-flow/SKILL.mdView on unpkg · L165Findings
Affected versions and remediation
This report applies to opencode-skills-collection@4.0.56.
See all versions of opencode-skills-collection for other recorded verdicts.
- Avoid installing opencode-skills-collection@4.0.56. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.