Package evidence

@impalasys/[email protected]

Install-time lifecycle script: postinstall="node ./chmod-bin.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: 3
First published: Jun 2026
Publisher: GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: −70% (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":["@impalasys/[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":["@impalasys/[email protected]"],"fail_on":"high"}'

PublisherGitHub Actions

Artifact bytes19,618,243

Previous version0.1.2

Published2026-06-04T14:47:47.499Z

SHA-2568fc6f1d9773e2b3e5b79b7cb388c834915224cac8071bcbb3a6c8bd6b950fe8d

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.3 vs 0.1.2: "node ./chmod-bin.js"

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

Availability ledger

available

high

11h agoLast checked

highRisk

45Score

0.1.3Version

Status history (1 event)

new → available11h ago · risk high · score 45 · status changed

Evidence

Static findings

1 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.3 vs 0.1.2: "node ./chmod-bin.js"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.3 vs 0.1.2: "node ./chmod-bin.js"	40
low	Install-time lifecycle script	package.json	postinstall="node ./chmod-bin.js"	5

Manifest

Package metadata

Scripts1

postinstallnode ./chmod-bin.js