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
- 2
- First published
- Jun 2026
- Publisher
- ankdev
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":["@clean-jsdoc-theme/[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":["@clean-jsdoc-theme/[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
Scripts9
buildnode scripts/build-css.mjs && tsupbuild:cssnode scripts/build-css.mjscleannode ../../scripts/clean.mjs dist .turboclean-node-modulesnode ../../scripts/clean.mjs node_modulesdevtsup --watchlinteslint srcsmoketsx scripts/smoke.tstestvitest runtypechecktsc --noEmit
Dependencies12
@clean-jsdoc-theme/rang^5.0.0-alpha.0@clean-jsdoc-theme/setu^5.0.0-alpha.0@clean-jsdoc-theme/utils^5.0.0-alpha.0@mdx-js/mdx^3.0.0@shikijs/rehype^4.2.0esbuild^0.21.5pagefind^1.1.0preact^10.22.0preact-render-to-string^6.5.13remark-frontmatter^5remark-gfm^4shiki^4.2.0