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"}'
Publishersshaaf
Artifact bytes27,184
Previous version1.0.3
Published2026-05-25T00:26:59.006Z
SHA-2565fff09fc9bd4956289856ca3b40e6db6c6d2703e87082b3b627aef63ab8e3bd4

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

Scripts8
  • buildnpm run build:css
  • build:csstailwindcss -i ./src/learnj.css -o ./_assets/website/learnj.css --minify
  • example:buildnpm run build --prefix example
  • example:installnpm install --prefix example
  • example:servenpm run serve --prefix example
  • prepacknpm run build
  • prepublishOnlynpm run build
  • watchtailwindcss -i ./src/learnj.css -o ./_assets/website/learnj.css --watch