PkgRadar

Package evidence

@gonzih/[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
7
First published
May 2026
Publisher
gonzih

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":["@gonzih/[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":["@gonzih/[email protected]"],"fail_on":"review"}'
Publishergonzih
Artifact bytes12,815
Previous version0.1.5
Published2026-06-11T05:58:18.966Z
SHA-2564a2eb606e05bc43c167fbdd25740307f9ae5bff3d6d9247dbab8855b85dd0439

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.6Version
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

Scripts4
  • buildrm -rf dist && npm run build:esm && npm run build:cjs
  • build:cjstsc -p tsconfig.cjs.json && node scripts/fix-cjs.mjs
  • build:esmtsc -p tsconfig.json
  • testnode --import tsx/esm --test src/channels.test.ts