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
- 1
- Versions published
- 5
- First published
- Aug 2025
- Publisher
- rushikesh_g25
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
buildtsupcleanrm -rf ./distdevtsup --watch --onSuccess "node dist/index.js"prepublishOnlynpm run clean && npm run buildstartnode dist/index.jstype-checktsc --noEmit
Dependencies17
@ai-sdk/google^1.2.22@clack/prompts^0.7.0@esm2cjs/execa6.1.1-cjs.1@google/genai^1.10.0@types/node^20.11.24ai^4.3.19cfonts^3.3.0chalk^4.0.0commander^12.1.0dotenv^17.2.0fs-extra^11.2.0glob^11.0.3prettier^3.2.5tsup^8.5.0type-fest^4.26.1typescript^5.8.3zod^3.23.8