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
- 2
- First published
- May 2026
- Publisher
- apohara
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":["@apohara/[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":["@apohara/[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
Scripts6
bench:djlnode test/djl-latency.bench.jsclinode bin/synthex.mjsdemonode demo/demo.jssamplenode scripts/gen-sample-report.mjsstartnode server.jstestnode --test
Dependencies13
@modelcontextprotocol/sdk1.21.2@opentelemetry/api^1.9.1@opentelemetry/exporter-metrics-otlp-http^0.218.0@opentelemetry/exporter-trace-otlp-http^0.218.0@opentelemetry/sdk-node^0.218.0asn1js^3.0.5fastmcp^3.33.0pdfkit^0.18.0pkijs^3.0.15playwright^1.60.0pvutils^1.1.3qrcode^1.5.4zod^3.23.0