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
- 6
- First published
- Feb 2026
- Publisher
- blankeos
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
Dependencies26
@bprogress/core^1.3.4@corvu/drawer^0.2.4@kobalte/core^0.13.11@shikijs/rehype^3.14.0@t3-oss/env-core^0.13.10@tailwindcss/vite^4.1.18bagon-hooks^0.0.6class-variance-authority^0.7.1clsx^2.1.1cmdk-solid^1.1.2flexsearch^0.8.212jsonc-parser^3.3.1rehype-autolink-headings^7.1.0rehype-katex^7.0.1rehype-slug^6.0.0remark-gfm^4.0.1remark-github-blockquote-alert^2.0.1remark-math^6.0.0solid-js1.9.11solid-jsx^1.1.4solid-sonner^0.2.8tailwind-merge^3.4.0vike^0.4.252vike-metadata-solid^1.0.5vike-solid^0.8.0zod^4.3.6