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.

Versions published
44Mature · −50% score
First published
Dec 2016
Publisher
mrmlnc

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"}'
Publishermrmlnc
Artifact bytes24,936
Previous version3.3.0
Published2023-07-22T08:45:26.553Z
SHA-2560dace4224a1f9878cfe3f005eab7aca89d7004e2f815886e7a8bbc2c041ba951

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
3.3.1Version
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
  • bench:asyncnpm run bench:product:async && npm run bench:regression:async
  • bench:productnpm run bench:product:async && npm run bench:product:sync && npm run bench:product:stream
  • bench:product:asynchereby bench:product:async
  • bench:product:streamhereby bench:product:stream
  • bench:product:synchereby bench:product:sync
  • bench:regressionnpm run bench:regression:async && npm run bench:regression:sync && npm run bench:regression:stream
  • bench:regression:asynchereby bench:regression:async
  • bench:regression:streamhereby bench:regression:stream
  • bench:regression:synchereby bench:regression:sync
  • bench:streamnpm run bench:product:stream && npm run bench:regression:stream
  • bench:syncnpm run bench:product:sync && npm run bench:regression:sync
  • buildnpm run clean && npm run compile && npm run lint && npm test
  • cleanrimraf out
  • compiletsc
  • linteslint "src/**/*.ts" --cache
  • testmocha "out/**/*.spec.js" -s 0
  • test:e2emocha "out/**/*.e2e.js" -s 0
  • test:e2e:asyncmocha "out/**/*.e2e.js" -s 0 --grep "\(async\)"
  • test:e2e:streammocha "out/**/*.e2e.js" -s 0 --grep "\(stream\)"
  • test:e2e:syncmocha "out/**/*.e2e.js" -s 0 --grep "\(sync\)"
  • watchnpm run clean && npm run compile -- --sourceMap --watch
Dependencies5
  • @nodelib/fs.stat^2.0.2
  • @nodelib/fs.walk^1.2.3
  • glob-parent^5.1.2
  • merge2^1.3.0
  • micromatch^4.0.4