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
- 18
- First published
- May 2026
- Publisher
- black-knight.dev
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":["@black-knight.dev/[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":["@black-knight.dev/[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
Scripts8
audit:promotionnode scripts/router/audit/audit-promotion-gates.mjsaudit:roadmapnode scripts/router/audit/audit-implementation-roadmap.mjschecknpm test && npm run audit:roadmap && npm run pack:drycheck:promotionnpm run audit:promotionevalnode --test test/eval-runner.test.jsmcpnode ./mcp/server.jspack:drynpm pack --dry-runtestnode --test
Dependencies7
@black-knight.dev/pinglet^0.2.0@extractus/article-extractor^8.1.0@mariozechner/pi-ai^0.73.1better-sqlite3^12.10.0pdfjs-dist^6.0.227turndown^7.2.4typebox^1.1.38