PkgRadar

Package evidence

[email protected]

Install Lifecycle Suppresses Failure: postinstall="node dist/cli/postinstall.js 2>/dev/null || true"

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
9
First published
May 2026
Publisher
anil7948

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"}'
Publisheranil7948
Artifact bytes90,481
Previous version1.0.5
Published2026-05-23T18:08:39.594Z
SHA-25647896b2a27da724e298b2ffe0b8f55123b43f555829a96d8b85e9a20afbc52de

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.1.0 vs 1.0.5: "node dist/cli/postinstall.js 2>/dev/null || true"

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

Availability ledger

available

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

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

anil7948

2 members · evidence strength 63

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.0 vs 1.0.5: "node dist/cli/postinstall.js 2>/dev/null || true"40
highInstall Lifecycle Suppresses Failurepackage.jsonpostinstall="node dist/cli/postinstall.js 2>/dev/null || true"20
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 25 day(s) ago, 9 total version(s), has lifecycle hook10
Show all 4 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.0 vs 1.0.5: "node dist/cli/postinstall.js 2>/dev/null || true"40
highInstall Lifecycle Suppresses Failurepackage.jsonpostinstall="node dist/cli/postinstall.js 2>/dev/null || true"20
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 25 day(s) ago, 9 total version(s), has lifecycle hook10
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node dist/cli/postinstall.js 2>/dev/null || true"5

Manifest

Package metadata

Scripts7
  • buildtsc -p tsconfig.json && chmod +x dist/cli/index.js
  • cleanrm -rf dist
  • devtsc -p tsconfig.json --watch
  • postinstallnode dist/cli/postinstall.js 2>/dev/null || true
  • prepublishOnlynpm run clean && npm run build
  • startnode dist/cli/index.js
  • typechecktsc -p tsconfig.json --noEmit
Dependencies7
  • @modelcontextprotocol/sdk^1.0.4
  • better-sqlite3^11.3.0
  • chalk^5.3.0
  • commander^12.1.0
  • ignore^5.3.2
  • ora^8.1.0
  • undici^6.20.0