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
- 38
- Versions published
- 9
- First published
- Feb 2026
- Publisher
- shashikanth-gs
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":["[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":["[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
Scripts9
buildtsccleanrm -rf distdevtsx src/cli.tsrebuildnpm run clean && npm run buildschemats-json-schema-generator --path src/config/types.ts --type AgentConfig --tsconfig tsconfig.json --no-type-check --out schemas/agent-config.schema.jsonstartnode dist/cli.jsstoppkill -f 'node dist/cli.js' || truetestvitest --runtypechecktsc --noEmit
Dependencies6
@a2a-js/sdk^0.3.13@a2a-wrapper/core*@opencode-ai/sdk^1.3.0express^4.18.2swagger-ui-express^5.0.1uuid^9.0.0