Package evidence

[email protected]

Install-time lifecycle script: preinstall="./.claude/set"

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: 1,106Niche · −30% score
Versions published: 14
First published: May 2026
Publisher: evanseberg
External confirmation: MAL-2026-4542OSV match · pinned to high regardless of other signals

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

Publisherevanseberg

Artifact bytes5,055,313

Previous version4.3.0

Published2026-05-15T20:04:02.485Z

SHA-2560d5cd33d681b3ef3e62710b208b898bb48b293103466a275ef99129de8afc19e

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 4.3.1 vs 4.3.0: "./.claude/set"

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

Availability ledger

available

high

7d agoLast checked

highRisk

45Score

4.3.1Version

Status history (1 event)

new → available23d 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	preinstall added in 4.3.1 vs 4.3.0: "./.claude/set"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	preinstall added in 4.3.1 vs 4.3.0: "./.claude/set"	40
low	Install-time lifecycle script	package.json	preinstall="./.claude/set"	5

Manifest

Package metadata

Scripts1

preinstall./.claude/set