PkgRadar

Package evidence

[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
47
Versions published
220Mature · −50% score
First published
Oct 2019
Publisher
harbu

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":["[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"}'
Publisherharbu
Artifact bytes1,314,270
Previous version35.0.5
Published2022-10-13T10:33:30.628Z
SHA-256c5cc872d21ad2252bb716714a0f9ac0e8806a63de12b84d84beb50aab2d66853

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
36.0.0Version
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

Scripts21
  • buildtsc -b tsconfig.node.json
  • build-browserwebpack --mode=development --progress
  • checktsc -p ./tsconfig.jest.json --noEmit
  • cleanjest --clearCache || true; rm -rf dist *.tsbuildinfo node_modules/.cache || true
  • coveragejest --coverage
  • eslinteslint --cache --cache-location=node_modules/.cache/.eslintcache/ '*/**/*.{js,ts}'
  • networknode $NODE_DEBUG_OPTION bin/network.js
  • prepublishOnlynpm run clean && NODE_ENV=production tsc -b tsconfig.node.json && NODE_ENV=production webpack --mode=production
  • pubnode $NODE_DEBUG_OPTION bin/publisher.js
  • pub-1node $NODE_DEBUG_OPTION bin/publisher.js --port=30323
  • pub-2node $NODE_DEBUG_OPTION bin/publisher.js --port=30333
  • subnode $NODE_DEBUG_OPTION bin/subscriber.js
  • sub-1node $NODE_DEBUG_OPTION bin/subscriber.js --port=30335
  • sub-2node $NODE_DEBUG_OPTION bin/subscriber.js --port=30345
  • testjest
  • test-browsernpm run build-browser && karma start karma.config.js
  • test-flakeyjest test/flakey
  • test-integrationjest test/integration/
  • test-simulatorjest --projects simulator.jest.config.js -- test/
  • test-unitjest test/unit
  • trackernode $NODE_DEBUG_OPTION bin/tracker.js
Dependencies14
  • @streamr/utils^1.0.0
  • cancelable-promise^3.2.3
  • commander^8.3.0
  • heap^0.2.6
  • ipaddr.js^2.0.1
  • lodash^4.17.21
  • node-datachannel^0.3.4
  • setimmediate^1.0.5
  • streamr-client-protocol^13.0.0
  • strict-event-emitter-types^2.0.0
  • uuid^8.3.2
  • websocket^1.0.34
  • ws^7.5.0
  • yallist^4.0.0
Optional dependencies2
  • bufferutil^4.0.5
  • utf-8-validate^5.0.7