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
301
Versions published
254Mature · −50% score
First published
Oct 2019
Publisher
streamr-dev

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"}'
Publisherstreamr-dev
Artifact bytes116,486
Previous version100.0.0-testnet-three.4
Published2024-02-13T12:46:24.133Z
SHA-256f8ab2c7b8d06cafa45c4d00653e3bd5b41d6dbda50d66899d8f3816cd70313a5

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
100.0.0-testnet-three.5Version
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
  • buildtsc -b tsconfig.node.json
  • checktsc -p ./tsconfig.jest.json --noEmit
  • cleanjest --clearCache || true; rm -rf dist *.tsbuildinfo node_modules/.cache || true
  • eslinteslint --cache --cache-location=node_modules/.cache/.eslintcache/ '*/**/*.{js,ts}'
  • testnpm run test-unit && npm run test-integration && npm run test-sequential
  • test-integrationjest --bail --forceExit test/integration && npm run test-sequential
  • test-sequentialjest --bail --forceExit --maxWorkers=1 test/sequential # always run sequential tests with maxWorkers=1
  • test-unitjest test/unit
Dependencies27
  • @ethersproject/hdnode^5.4.0
  • @inquirer/prompts^3.3.0
  • @streamr/config^5.1.2
  • @streamr/network-contracts^7.0.7
  • @streamr/protocol100.0.0-testnet-three.5
  • @streamr/utils100.0.0-testnet-three.5
  • aedes^0.51.0
  • ajv^8.8.2
  • ajv-formats^2.1.1
  • cassandra-driver^4.7.2
  • chalk^4.0.0
  • commander^11.1.0
  • consistent-hash^1.1.1
  • cors^2.8.5
  • ethers^5.4.7
  • express^4.17.1
  • heap^0.2.6
  • lodash^4.17.21
  • merge2^1.4.1
  • nat-type-identifier^2.0.9
  • node-fetch^2.7.0
  • p-limit^3.1.0
  • qs^6.10.1
  • streamr-client100.0.0-testnet-three.5
  • uuid^9.0.1
  • ws^8.16.0
  • zod^3.22.4