Skills/npm/npm-release-kit

npm-release-kit@0.1.4

CAUTION

Publisher claims: "Token-free npm releases through GitHub Actions trusted publishing, with portable Agent skills." Observed in sandbox: static analysis only — behavior not yet observed.

Registry npm (MCP server)Publisher petercjl · joined 6 days agoInstalls 762Last detonated 6d ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-27 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This 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

LOW
Unpinned dependencytemplates/publish-npm.yml:40 · Unpinned dependencyFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
AST06
MEDIUM
npx invocation of non-well-known packagetemplates/publish-npm.yml:49 · npx invocation of non-well-known package — may execute untrusted codeFix: Pin versions and sources; vendor anything fetched at install time.
AST06

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim petercjl: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
  3. Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.
  4. Unpinned dependency≈ +1 on the totalPin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim petercjl