Package evidence

[email protected]

Remote Payload: matched "github.com/esm-dev/esm.sh/releases/download"

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: 28
Versions published: 21Mature · −50% score
First published: Mar 2023
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":["[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"}'

PublisherGitHub Actions

Artifact bytes2,183

Previous version0.0.6

Published2026-06-11T03:12:55.092Z

SHA-25645eede4b839ddcaf953ac889f0850ec8870d78033992b6618378ccacdb1a151e

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.1 vs 0.0.6: "node install.mjs"

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

Availability ledger

available

high

13h agoLast checked

highRisk

69Score

0.1.1Version

Status history (1 event)

new → available13h ago · risk high · score 69 · status changed

Evidence

Static findings

3 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.1 vs 0.0.6: "node install.mjs"	40
medium	Remote Payload	package/install.mjs	matched "github.com/esm-dev/esm.sh/releases/download"	12
medium	Remote Payload	package/bin/esm.sh	matched "github.com/esm-dev/esm.sh/releases/download"	12

Show all 4 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.1 vs 0.0.6: "node install.mjs"	40
medium	Remote Payload	package/install.mjs	matched "github.com/esm-dev/esm.sh/releases/download"	12
medium	Remote Payload	package/bin/esm.sh	matched "github.com/esm-dev/esm.sh/releases/download"	12
low	Install-time lifecycle script	package.json	postinstall="node install.mjs"	5

Manifest

Package metadata

Scripts1

postinstallnode install.mjs

Optional dependencies6

@esm.sh/cli-darwin-arm640.1.1
@esm.sh/cli-darwin-x640.1.1
@esm.sh/cli-linux-arm640.1.1
@esm.sh/cli-linux-x640.1.1
@esm.sh/cli-win32-arm640.1.1
@esm.sh/cli-win32-x640.1.1