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
- 1
- First published
- Jun 2026
- Publisher
- dknguyen
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":["@boltz.one/[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":["@boltz.one/[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
Scripts 5
Sign in to view install / lifecycle script contents.
Dependencies15
@boltz.one/contracts^0.1.0@boltz.one/sdk-core^0.1.0@opentelemetry/api^1.9.0@opentelemetry/auto-instrumentations-node^0.52.0@opentelemetry/exporter-prometheus^0.55.0@opentelemetry/exporter-trace-otlp-http^0.55.0@opentelemetry/resources^1.0.0@opentelemetry/sdk-node^0.55.0@opentelemetry/semantic-conventions^1.0.0drizzle-orm^0.36.0hono^4.6.0ioredis^5.4.1jose^5.9.6postgres^3.4.5zod^3.23.8