PkgRadar

Package evidence

[email protected]

no findings

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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"}'
Publisherjainishgodhani
Artifact bytes26,150
Previous version1.0.10
Published2026-05-25T03:24:33.754Z
SHA-256d9f5e6eddb88e1066ae41be5c9aedff0a3375c378fca0fedc8a3d55d062d6301

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

low
Last checked
lowRisk
0Score
1.0.11Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts3
  • devnode ./cli.js
  • smokenode ./cli.js --help
  • startnode ./cli.js
Dependencies8
  • chalk^5.6.2
  • commander^14.0.2
  • concurrently^9.2.1
  • execa^9.6.0
  • fs-extra^11.3.2
  • inquirer^12.10.0
  • ora^9.0.0
  • validate-npm-package-name^6.0.2