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"}'
Publisherkeyserdsoze
Artifact bytes92,623
Previous version0.1.49
Published2026-04-25T22:20:47.375Z
SHA-256968e15de19fd1dd4de005b570007ea190525729e428cbb5920ac2fb4973d7c05

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.50Version
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
  • buildnpm run build:cli && npm run export:epub && astro build
  • build:clitsc -p tsconfig.cli.json
  • devnode ./scripts/dev.mjs
  • doctornode ./scripts/doctor.mjs
  • export:epubnode ./scripts/export-epub.mjs
  • previewastro preview
  • testnpm run build:cli && node --test test/**/*.test.mjs
Dependencies4
  • astro^5.14.1
  • chokidar^4.0.3
  • marked^16.3.0
  • narrarium^0.1.27