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
- Mar 2026
- Publisher
- boomslag
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":["@apholdings/[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":["@apholdings/[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
Scripts4
buildtsgo -p tsconfig.build.json && shx chmod +x dist/main.jscleanshx rm -rf distdevtsgo -p tsconfig.build.json --watch --preserveWatchOutputprepublishOnlynpm run clean && npm run build -w @apholdings/jensen-ai -w @apholdings/jensen-agent-core -w @apholdings/jensen-code && npm run build
Dependencies10
@anthropic-ai/sandbox-runtime^0.0.16@apholdings/jensen-agent-core1.0.7@apholdings/jensen-ai1.0.7@apholdings/jensen-code1.0.7@sinclair/typebox^0.34.0@slack/socket-mode^2.0.0@slack/web-api^7.0.0chalk^5.6.2croner^9.1.0diff^8.0.2