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.

Weekly downloads
44
Versions published
10
First published
Feb 2026
Publisher
kyr0

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"}'
Publisherkyr0
Artifact bytes232,586
Previous version0.6.3
Published2026-05-30T22:11:14.379Z
SHA-256d84e67d0102f2e30c0c6428d9513ce11655bf880eae7ac5c9fcfcf542205bd83

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

Scripts7
  • buildpkgroll --sourcemap --packagejson='*.js' --packagejson='*.mjs' --packagejson='*.cjs' --packagejson='*.d.ts' --packagejson='*.d.mts' --packagejson='*.d.cts'
  • cleanrm -rf ./dist && rm -rf ./node_modules/.bun
  • postbuildbunx tsx scripts/build-css.ts
  • prebuildbun run clean
  • prepublishOnlybun run test
  • pretestbun run build
  • testvitest run --config vitest.browser.config.ts