PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: postinstall="node scripts/ensure-electron.cjs"

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
9
First published
Jun 2026
Publisher
twilson63

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 tarballAdd 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"}'
Publishertwilson63
Artifact bytes3,073,870
Previous version0.1.4
Published2026-06-01T19:34:32.275Z
SHA-25621572ea4eb581e6e2627843397f683bc1c28d946ea4eaa0da6bf50a73184789b

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.5 vs 0.1.4: "node scripts/ensure-electron.cjs"

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

Availability ledger

available

high
Last checked
highRisk
45Score
0.1.5Version
Status history (2 events)
  1. new → available · risk high · score 45 · status changed
  2. new → available · risk high · score 45 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.1.5 vs 0.1.4: "node scripts/ensure-electron.cjs"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.1.5 vs 0.1.4: "node scripts/ensure-electron.cjs"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node scripts/ensure-electron.cjs"5

Manifest

Package metadata

Scripts12
  • buildnpm run gleam:build && vite build
  • checknode --check electron/main.cjs && node --check electron/pi-adapter.cjs && node --check renderer/main.js && npm test
  • devnpm run gleam:build && concurrently -k -n vite,electron -c cyan,green "npm:dev:web" "npm:dev:electron"
  • dev:electronwait-on http://127.0.0.1:5173 && HYPER_DESK_DEV=1 electron .
  • dev:webvite --host 127.0.0.1
  • distnpm run build && electron-builder
  • gleam:buildgleam build --target javascript
  • packnpm run build && electron-builder --dir
  • postinstallnode scripts/ensure-electron.cjs
  • releasenpm run build && electron-builder --publish always
  • startnpm run build && electron .
  • testgleam test && npm run build
Dependencies6
  • @earendil-works/pi-coding-agent^0.78.0
  • chrome-remote-interface^0.34.0
  • dompurify^3.4.7
  • electron42.3.0
  • marked^18.0.4
  • typebox^1.1.39