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
- 2
- First published
- Jun 2026
- Publisher
- cramforce
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":["@agent-harness-experimental/[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":["@agent-harness-experimental/[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
Scripts6
buildtsc -p tsconfig.build.json && tsx ../../scripts/copy-package-assets.ts packages/adapter-claude-managed-agentslintbiome check src package.json tsconfig.json tsconfig.build.jsontestvitest run --config ../../vitest.package.config.ts src/*.test.tstest:livetsx -r dotenv/config src/live-smoke.tstest:live:sandboxtsx -r dotenv/config src/live-sandbox-smoke.tstypechecktsc --noEmit -p tsconfig.json
Dependencies4
@agent-harness-experimental/sandbox-vercelworkspace:*@anthropic-ai/sdk^0.93.0agent-harness-experimentalworkspace:*zod^4.3.6