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
- 244
- Versions published
- 22
- First published
- Feb 2026
- Publisher
- iodwise
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
buildtsupdevtsup --watchprepackpnpm buildtestvitest runtest:coveragevitest run --coveragetypechecktsc --noEmit
Dependencies19
@ai-sdk/amazon-bedrock^4.0.77@ai-sdk/anthropic^3.0.79@ai-sdk/google^3.0.30@ai-sdk/openai^3.0.65@ai-sdk/openai-compatible^2.0.48@aws-sdk/credential-providers^3.1004.0@inquirer/core^11.1.4@inquirer/input^5.0.8@inquirer/password^5.0.8@inquirer/search^4.1.3@inquirer/select^5.1.0ai^6.0.97bash-tool^1.3.15better-sqlite3^12.10.0chalk^5.6.2cli-progress^3.12.0commander^14.0.3execa^9.6.1just-bash^2.10.2