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
- 1
- First published
- Jun 2026
- Publisher
- yohanesvito
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
Scripts6
buildbun build bin/mbg-cli.ts --target=node --outfile=dist/mbg-cli.js --external=viem && chmod +x dist/mbg-cli.jsclibun run bin/mbg-cli.tsdemobun run bin/mbg-cli.ts catalog list && bun run bin/mbg-cli.ts list-protocols && bun run bin/mbg-cli.ts score-protocol aave-v3-mantle && bun run bin/mbg-cli.ts score-route '[{"protocolId":"aave-v3-mantle","actionType":1,"amount":"1000"},{"protocolId":"meth-protocol","actionType":3,"amount":"500"}]'harnessbun run harness/agent-demo.tsprepublishOnlybun run buildtypechecktsc --noEmit
Dependencies1
viem^2.21.0