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
- 12
- Versions published
- 5
- First published
- Mar 2026
- Publisher
- kyr0
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts5
buildpkgroll --sourcemapcleanrm -rf ./dist && rm -rf ./node_modules/.bunprebuildbun run cleanprepublishOnlybun run buildtestecho 'No tests available'
Dependencies13
@mdx-js/rollup^3.1.0@tailwindcss/vite^4.1.18chokidar^5.0.0defuss^3.4.4defuss-vite^1.1.3fast-glob^3.3.3rehype-katex^7.0.1remark-frontmatter^5.0.0remark-gfm^4.0.1remark-math^6.0.0remark-mdx-frontmatter^5.2.0tailwindcss^4.1.18vite^7.3.1