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
- 725
- Versions published
- 7
- First published
- May 2026
- Publisher
- brentfriedman
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":["@rubric-app/[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":["@rubric-app/[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 (2 events)
- available → available · risk low · score 0 · status available -> available, risk high -> low, score 45 -> 0
- new → available · risk high · score 45 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts3
buildtsc -p tsconfig.jsontestpnpm build && RUBRIC_INTERNAL_ALLOW_LOOPBACK_FOR_TESTS=1 node --test test/*.test.mjstypechecktsc -p tsconfig.json --noEmit
Dependencies2
re2^1.24.1zod^3.23.8