opencode-skills-collection@4.1.9
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
Manual ReviewIndependent AI assessment: manual_review. LPM AI review remains unresolved.
Verified text source was inspected, but required binary or non-UTF8 files remain unresolved: bundled-skills/theme-factory/theme-showcase.pdf. A clean verdict cannot be grounded.
Independent scan evidence
public snapshot- The only manifest lifecycle script is prepublishOnly, which runs the build.
- The signup skill contains ordinary UX guidance.
- The Playwright runner executes code supplied by its caller; the Electron drive sends commands to a loopback service.
- The Apify example reads APIFY_TOKEN and sends it to api.apify.com for the actor selected by the caller.
- The Hugging Face example sends HF_TOKEN to huggingface.co, its intended service.
- The PDF is documented as a viewing asset; the Fedora test uses a temporary HOME, and the research workflow receives a user-provided question.
Source & flagged code
13 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.1.9.
See all versions of opencode-skills-collection for other recorded verdicts.
- Avoid installing opencode-skills-collection@4.1.9. 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.