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
- 14
- First published
- May 2026
- Publisher
- ukanwat
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":["@openacme/[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":["@openacme/[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 --buildcheck-typestsc --noEmitdevnode scripts/dev.mjsstartnode dist/index.jstestvitest runtest:e2evitest run --config vitest.e2e.config.ts
Dependencies20
@hono/node-server^1.14.0@openacme/agent-catalog0.11.0@openacme/agent-core0.11.0@openacme/auth0.11.0@openacme/browser0.11.0@openacme/config0.11.0@openacme/db0.11.0@openacme/llm-provider0.11.0@openacme/mcp-client0.11.0@openacme/memory0.11.0@openacme/skills0.11.0@openacme/tasks0.11.0@openacme/tool-host0.7.5@openacme/tools0.11.0ai^6.0.177croner^10.0.1dotenv^16.5.0hono^4.7.0web-push^3.6.7zod^4.1.8