PkgRadar

Package evidence

@bbn/[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
248
Versions published
706Mature · −50% score
First published
Oct 2023
Publisher
nabab

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.

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":["@bbn/[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":["@bbn/[email protected]"],"fail_on":"review"}'
Publishernabab
Artifact bytes1,392,518
Previous version2.0.239
Published2026-05-19T01:56:50.867Z
SHA-25601c66d5dd2750fb16f2d4f5753b00230e094fbd56362a5e4a9270879ba666149

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
2.0.240Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts8
  • allnpm run type && npm run test && npm run gitauto && npm version patch && npm run build && npm run gitend && npm publish
  • build./node_modules/.bin/rollup -c
  • gitautogit stage ./src/* ./*.ts ./*.json ./*.config.js ./test/*.mjs && git stage -f ./dist/* && git commit -m "Latest changes"
  • gitendgit stage ./package.json && git stage -f ./dist/* && git commit -m "Latest changes" && git push
  • pubnpm version patch && npm publish
  • testIS_TESTING=true npx mocha
  • type./node_modules/.bin/tsc
  • wtfecho "Error: no test specified" && exit 1
Dependencies5
  • @formatjs/intl-datetimeformat^6.18.2
  • @formatjs/intl-pluralrules^5.4.6
  • @formatjs/intl-relativetimeformat^11.4.13
  • cldr-core^48.0.0
  • temporal-polyfill^0.3.0