PkgRadar

Package evidence

@bigbinary/[email protected]

no findings

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
3,823Niche · −30% score
Versions published
1,067Mature · −50% score
First published
Mar 2023
Publisher
neetohq

Effective trust discount applied: 50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

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":["@bigbinary/[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":["@bigbinary/[email protected]"],"fail_on":"review"}'
Publisherneetohq
Artifact bytes4,284,886
Previous version5.1.28
Published2026-06-12T08:21:39.213Z
SHA-256ec61ecc2cf8c3563ecf955df5b0187690838eacd26bb196a4a63809971a8d90d

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

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

Availability ledger

available

low
Last checked
lowRisk
0Score
5.1.29Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts9
  • buildNODE_ENV=production NODE_OPTIONS=--max-old-space-size=3500 storybook build
  • build:jsdocnode ./.scripts/jsdoc-builder.mjs
  • bundleNODE_ENV=production yarn build:jsdoc && NODE_ENV=production rollup --bundleConfigAsCjs -c rollup.config.js --environment production
  • preparehusky install
  • servenode .storybook/db
  • storybookbash -c "trap 'kill 0' SIGINT; node .storybook/db & NODE_ENV=development storybook dev -p 6006"
  • sync_with_wheel./.scripts/sync_with_wheel.sh
  • testTZ=UTC jest
  • watchrollup --bundleConfigAsCjs -c rollup.config.js --watch