PkgRadar

Package evidence

[email protected]

no findings

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
4
First published
Jun 2026
Publisher
himanshud2611

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"}'
Publisherhimanshud2611
Artifact bytes22,785
Previous version0.1.2
Published2026-06-05T23:59:20.955Z
SHA-256fe50b6c645fa2b3b86af0013a19291e4e4a6ee30744d8f01e0e7db7a53bf33ca

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
0.1.3Version
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

Scripts12
  • analyzenode dist/src/cli.js analyze
  • buildtsc -p tsconfig.json
  • checktsc -p tsconfig.json --noEmit
  • devtsx src/cli.ts
  • inspectnode dist/src/cli.js inspect
  • lensnode dist/src/cli.js
  • prepacknpm run build
  • prepublishOnlynpm run check && npm run build
  • runnode dist/src/cli.js run
  • scannode dist/src/cli.js scan
  • startnode dist/src/cli.js
  • testnode --test dist/**/*.test.js