Package evidence

[email protected]

Install-time lifecycle script: postinstall="patch-package"

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: 5
First published: May 2026
Publisher: as3long

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

Publisheras3long

Artifact bytes236,211

Previous version0.1.3

Published2026-05-29T03:02:17.308Z

SHA-256cd0874301f1b62cc0fa0d52e982e7f0aafc2c610edcf16cf0c45967cebc39ae1

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.5 vs 0.1.3: "patch-package"

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

Availability ledger

not present

status

3d agoLast checked

noneRisk

—Score

0.1.5Version

Latest scanner note: [email protected] not present in registry metadata

Status history (2 events)

available → not_present17d ago · risk none · score — · [email protected] not present in registry metadata
new → available19d 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.5 vs 0.1.3: "patch-package"	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.5 vs 0.1.3: "patch-package"	40
low	Install-time lifecycle script	package.json	postinstall="patch-package"	5

Manifest

Package metadata

Scripts13

buildtsc && npm run copy:web
checkbiome check .
check:fixbiome check --fix .
copy:webnode -e "const fs=require('fs'),p=require('path');const src=p.join('src','web','public');const dst=p.join('dist','web','public');if(fs.existsSync(src)){if(!fs.existsSync(dst))fs.mkdirSync(dst,{recursive:true});for(const f of fs.readdirSync(src)){fs.copyFileSync(p.join(src,f),p.join(dst,f))}}"
devtsx src/index.ts
formatbiome format --write .
lintbiome lint .
lint:fixbiome lint --fix .
postinstallpatch-package
preparehusky
startnode dist/index.js
testvitest run
test:watchvitest

Dependencies7

@anthropic-ai/sdk^0.30.0
@earendil-works/pi-tui0.75.5
adm-zip^0.5.17
commander^12.0.0
openai^4.0.0
ws^8.21.0
zod^3.23.0