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
- 414
- Versions published
- 60Mature · −50% score
- First published
- Jun 2019
- Publisher
- mbklein
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 monitoringNo 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":["[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"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts12
buildtsupbuild:watchtsup --watchcleanrm -rf node_modules/ vendor/ coverage/ dist/linteslint "{src,tests}/**/*.{js,ts}"lint:examplescd examples/tiny-iiif && npm run lintlint:fixeslint --fix "{src,tests}/**/*.{js,ts}"preparenpm run buildtestnode scripts/test.js --env=nodetest:coveragenode scripts/test.js --env=node --coveragetypechecktsc -p tsconfig.json --noEmittypecheck:stricttsc -p tsconfig.strict.json --noEmitvalidatenpm run build && concurrently -s !command-server -k -n server,iiif --hide server -c blue,green "cd examples/tiny-iiif && npm run validator" "cd validator && sleep 2 && uv run ./run-validator.sh"
Dependencies2
debug^4.3.4mime-types2.x
Optional dependencies1
sharp^0.34.4