PkgRadar

Package evidence

[email protected]

Manifest Codeless Dependency Stub: package ships no JS/TS source but declares 3 dependency(ies) (0 with loose/empty version specs) — dependency-confusion / install-chain loader shape

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Weekly downloads
47
Versions published
8
First published
Mar 2026
Publisher
bgoodman

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["[email protected]"],"fail_on":"high"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["[email protected]"],"fail_on":"high"}'
Publisherbgoodman
Artifact bytes834,168
Previous version0.1.6
Published2026-05-25T19:33:25.483Z
SHA-2561045192076541065c433ab94d8c695c37d58b787c3ccde2e84a4e5321d65308a

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.7 vs 0.1.6: "node scripts/deprecation-warning.mjs"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

high
Last checked
highRisk
60Score
0.1.7Version
Status history (2 events)
  1. availableavailable · risk high · score 60 · status available -> available, risk high -> high, score 45 -> 60
  2. newavailable · risk high · score 45 · status changed

Evidence

Static findings

3 static · 1 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.1.7 vs 0.1.6: "node scripts/deprecation-warning.mjs"40
mediumManifest Codeless Dependency Stubpackage.jsonpackage ships no JS/TS source but declares 3 dependency(ies) (0 with loose/empty version specs) — dependency-confusion / install-chain loader shape15
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 83 day(s) ago, 8 total version(s), has lifecycle hook10
Show all 4 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.1.7 vs 0.1.6: "node scripts/deprecation-warning.mjs"40
mediumManifest Codeless Dependency Stubpackage.jsonpackage ships no JS/TS source but declares 3 dependency(ies) (0 with loose/empty version specs) — dependency-confusion / install-chain loader shape15
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 83 day(s) ago, 8 total version(s), has lifecycle hook10
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node scripts/deprecation-warning.mjs"5

Manifest

Package metadata

Scripts5
  • buildtsc && npm run copyIcons
  • copyIconsnode scripts/copy-icons.mjs
  • postinstallnode scripts/deprecation-warning.mjs
  • testvitest run
  • test:watchvitest
Dependencies3
  • @modelcontextprotocol/sdk^1.27.1
  • elkjs^0.11.1
  • zod^3.24.2