Package evidence

[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""

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: 13,676Mainstream · −50% score
Versions published: 13Established · −30% score
First published: May 2011
Publisher: iliakan

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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 tarball Add 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"}'

Publisheriliakan

Artifact bytes4,833

Previous version0.1.3

Published2026-05-28T05:02:42.099Z

SHA-2563ff998f54a0184604f2ffffd001ed848004c10165e4ba50f164473adfd484af8

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.4 vs 0.1.3: "node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""

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

Availability ledger

available

high

3d agoLast checked

highRisk

75Score

0.1.4Version

Status history (2 events)

available → available13d ago · risk high · score 75 · status available -> available, risk high -> high, score 45 -> 75
new → available16d ago · risk high · score 45 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.4 vs 0.1.3: "node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""	30

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.4 vs 0.1.3: "node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""	30
low	Install-time lifecycle script	package.json	postinstall="node -e \"console.log('\\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\\n')\""	5

Manifest

Package metadata

Scripts1

postinstallnode -e "console.log('\nNotice: this module will be rewritten and changed. Consider switching to nodemon.\n')"

Dependencies1

inotify>= 0.1.6