Package evidence
[email protected]
New Account With Lifecycle Hook: package first published 0 day(s) ago, 2 total version(s), has lifecycle hook
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
- 2
- First published
- Jun 2026
- Publisher
- jmclaughlin724
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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"}'Why flagged
What the scanner saw
New Account With Lifecycle Hook: package first published 0 day(s) ago, 2 total version(s), has lifecycle hook
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk high · score 15 · status changed
Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Account With Lifecycle Hook | package.json | package first published 0 day(s) ago, 2 total version(s), has lifecycle hook | 25 |
| medium | Suspicious Publish Context | manifest | {"package_age_days":0,"publisher":"jmclaughlin724","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true} | 10 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Account With Lifecycle Hook | package.json | package first published 0 day(s) ago, 2 total version(s), has lifecycle hook | 25 |
| medium | Suspicious Publish Context | manifest | {"package_age_days":0,"publisher":"jmclaughlin724","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true} | 10 |
| low | Install-time lifecycle script | package.json | postinstall="node bin/postinstall.mjs" | 5 |
Manifest
Package metadata
Scripts19
bench:comparenpm run build && node benchmarks/compare.jsbench:plotnode benchmarks/plot.jsbenchmarknpm run build && node dist/benchmark.jsbuildtsc -p tsconfig.json && node dist/config-schema-gen.jschecknpm run lint && npm run typecheck && npm test && npm run buildcheck:packagepublint && attw --pack . --profile esm-onlycleanrm -rf dist coveragecorpus:checknpm run build && node dist/cli.js corpus --corpus-dir corpus/supabase-styledocs:apitypedoc src/index.ts --out api-docsfixture:diffnode dist/cli.js diff --from dir:tests/fixtures/basic/from --to dir:tests/fixtures/basic/to --out stdoutfixture:verifynpm run build && out=$(mktemp -d)/basic.sql && node dist/cli.js diff --from dir:tests/fixtures/basic/from --to dir:tests/fixtures/basic/to --out "$out" && node dist/cli.js verify --from dir:tests/fixtures/basic/from --to dir:tests/fixtures/basic/to --migration "$out"formatbiome check --write .lintbiome check .pack:drynpm pack --dry-runpostinstallnode bin/postinstall.mjspreparenpm run buildtestvitest runtest:coveragevitest run --coveragetypechecktsc -p tsconfig.json --noEmit
Dependencies5
commander^14.0.3libpg-query^17.7.3pg^8.21.0pgsql-deparser^17.18.3zod^4.4.3