PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: postinstall="node scripts/postinstall.js"

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.

Versions published
5
First published
Dec 2013
Publisher
johno-stripe

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.

Inspect tarballAdd to CI gate
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"}'
Publisherjohno-stripe
Artifact bytes965
Previous version0.1.0
Published2026-05-29T01:46:10.030Z
SHA-256c9f1b6e6309f337fa9b3e10fe338986f579f3662f7aabd9bba220e002c0ede4e

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.2.0 vs 0.1.0: "node scripts/postinstall.js"

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

Availability ledger

available

high
Last checked
highRisk
45Score
0.2.0Version
Status history (2 events)
  1. available → available · risk high · score 45 · status available -> available, risk high -> high, score 75 -> 45
  2. new → available · risk high · score 75 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.2.0 vs 0.1.0: "node scripts/postinstall.js"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.2.0 vs 0.1.0: "node scripts/postinstall.js"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node scripts/postinstall.js"5

Manifest

Package metadata

Scripts1
  • postinstallnode scripts/postinstall.js