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
- 29
- Versions published
- 21
- First published
- Feb 2026
- Publisher
- well-prado
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":["@blokjs/[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":["@blokjs/[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
Scripts5
buildrimraf ./dist && tscdevbun --watch run src/index.tsstartbun run dist/index.jstestvitest runtest:devvitest
Dependencies15
@blokjs/api-call^0.6.18@blokjs/helper^0.6.18@blokjs/if-else^0.6.18@blokjs/runner^0.6.18@blokjs/shared^0.6.18@blokjs/trigger-worker^0.6.18@opentelemetry/api^1.9.0@opentelemetry/exporter-prometheus^0.57.2@opentelemetry/resources^1.30.1@opentelemetry/sdk-metrics^1.30.1@opentelemetry/sdk-trace-base^1.30.1@opentelemetry/semantic-conventions^1.39.0nats^2.28.0uuid^11.1.0zod^3.24.2