PkgRadar

Package evidence

@jaggle/[email protected]

Install-time lifecycle script: postinstall="node npm-install.cjs"

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
21
First published
May 2026
Publisher
jaggle
External confirmation
MAL-2026-4288OSV match · pinned to high regardless of other signals

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":["@jaggle/[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":["@jaggle/[email protected]"],"fail_on":"high"}'
Publisherjaggle
Artifact bytes17,833
Previous version1.0.18
Published2026-05-25T13:17:14.600Z
SHA-256b188dfa35119592d8f9bfa1ac89cba564d2e22b89b0df4c9a4c17fcccc66c84c

Why flagged

What the scanner saw

Install-time lifecycle script: postinstall="node npm-install.cjs"

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

Availability ledger

available

high
Last checked
highRisk
5Score
1.0.19Version
Status history (5 events)
  1. available → available · risk high · score 5 · status available -> available, risk high -> high, score 3 -> 5
  2. available → available · risk high · score 3 · status available -> available, risk high -> high, score 35 -> 3
  3. available → available · risk high · score 35 · status available -> available, risk high -> high, score 3 -> 35
  4. available → available · risk high · score 3 · status available -> available, risk review -> high, score 5 -> 3
  5. new → available · risk review · score 5 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node npm-install.cjs"5

Manifest

Package metadata

Scripts1
  • postinstallnode npm-install.cjs