PkgRadar

Package evidence

[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"manuelferegrino","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

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
manuelferegrino

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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

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":"review"}'
Publishermanuelferegrino
Artifact bytes69,347
Previous version0.2.0
Published2026-06-13T02:26:27.794Z
SHA-2563b7e6cc38751bc81905e70ccf0d56c237e18f1fcffa6cebaa97ea1f219ed8c6a

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"manuelferegrino","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}

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

Availability ledger

available

review
Last checked
reviewRisk
10Score
0.3.0Version
Status history (1 event)
  1. new → available · risk review · score 10 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":0,"publisher":"manuelferegrino","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}10

Manifest

Package metadata

Scripts13
  • buildbun run build:esm && bun run build:cjs && bun run build:browser && bun run build:types
  • build:browserbun build ./src/index.ts ./src/react/index.ts --outdir ./dist/browser --target browser --format esm --splitting --external react
  • build:cjsbun build ./src/index.ts ./src/react/index.ts ./src/node/index.ts --outdir ./dist/cjs --target node --format cjs --external react --entry-naming '[dir]/[name].cjs' --chunk-naming '[name]-[hash].cjs'
  • build:esmbun build ./src/index.ts ./src/react/index.ts ./src/node/index.ts --outdir ./dist/esm --target node --format esm --splitting --external react
  • build:typestsc -p tsconfig.build.json && for f in index react/index node/index; do cp "dist/types/$f.d.ts" "dist/types/$f.d.cts"; cp "dist/types/$f.d.ts.map" "dist/types/$f.d.cts.map"; done
  • cleanrm -rf dist
  • preparebun run build
  • prepublishOnlybun run clean && bun run build
  • testbun test
  • test:e2eLIVE_TESTS=1 bun test test/e2e/
  • test:integrationbun test test/integration/
  • test:unitbun test test/unit/
  • typechecktsc --noEmit