Recommended action
Block this updateStatic 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"}'Why flagged
What the scanner saw
Install-time lifecycle script: postinstall="node install.js"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
not present
Latest scanner note: [email protected] not present in registry metadata
Status history (2 events)
- available → not_present · risk none · score — · [email protected] not present in registry metadata
- new → available · risk high · score 72 · status changed
Related candidates
Linked campaigns and clusters
malleshmadapathi
3 members · evidence strength 68Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Install-time lifecycle script | package.json | postinstall="node install.js" | 30 |
| high | Install Lifecycle Remote Or Exec | package.json | postinstall="node install.js" | 30 |
| medium | Remote Payload | package/install.js | matched "github.com/${REPO}/releases/download" | 12 |
Manifest
Package metadata
Scripts1
postinstallnode install.js