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
- 39
- First published
- Apr 2026
- Publisher
- jallenhou
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@easbot/[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":["@easbot/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "AWS_ACCESS_KEY"
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 review · score 10 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/chunks/chunk-YGFGAD5H.mjs | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/dist/chunks/models-snapshot-XTWYGG3T.mjs | matched "GOOGLE_APPLICATION_CREDENTIALS" | 5 |
Manifest
Package metadata
Scripts24
buildtsup --env.NODE_ENV productioncleannpx rimraf dist node_modulesdevcross-env NODE_ENV=development tsx src/cli.ts -- tuiformatbiome format .format:fixbiome format --write .lintbiome check .lint:fixbiome check --write .lint:fix:unsafebiome check --write --unsafe ./srclint:reportbiome check --reporter=summary .publish:npmbash scripts/publish.shpublish:npm:winpowershell -ExecutionPolicy Bypass -File scripts/publish.ps1startcross-env NODE_ENV=production node dist/cli.mjs tui --newtestvitesttest:coveragevitest run --coveragetest:e2evitest run --config ./vitest.e2e.config.tstest:e2e:watchvitest --config ./vitest.e2e.config.tstest:integrationvitest run --config ./vitest.integration.config.tstest:integration:watchvitest --config ./vitest.integration.config.tstest:runvitest runtest:uivitest --uitest:unitvitest run --config ./vitest.unit.config.tstest:unit:watchvitest --config ./vitest.unit.config.tstest:watchvitest --watchtype-checktsc --noEmit
Dependencies90
@agentclientprotocol/sdk^0.25.0@ai-sdk/alibaba^1.0.23@ai-sdk/amazon-bedrock^4.0.105@ai-sdk/anthropic^3.0.77@ai-sdk/azure^3.0.64@ai-sdk/cerebras^2.0.51@ai-sdk/cohere3.0.35@ai-sdk/deepinfra^2.0.51@ai-sdk/deepseek^2.0.35@ai-sdk/gateway^3.0.114@ai-sdk/google^3.0.73@ai-sdk/google-vertex^4.0.128@ai-sdk/groq^3.0.39@ai-sdk/mistral^3.0.37@ai-sdk/openai^3.0.63@ai-sdk/openai-compatible^2.0.47@ai-sdk/perplexity^3.0.33@ai-sdk/provider^3.0.10@ai-sdk/provider-utils^4.0.27@ai-sdk/togetherai^2.0.51@ai-sdk/vercel^2.0.49@ai-sdk/xai^3.0.90@aws-sdk/credential-providers^3.1047.0@clack/prompts^1.4.0@easbot/codebase0.2.40@easbot/gateway0.2.40@easbot/local-model-sdk0.2.40@easbot/mcp0.2.40@easbot/memory0.2.40@easbot/note0.2.40- …and 60 more.