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
- 3
- First published
- Jun 2026
- Publisher
- mzhang0
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":["@leandown/[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":["@leandown/[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
Scripts4
buildbun run build:js && bun run build:dts && bun run build:templatesbuild:dtstsc -p tsconfig.build.jsonbuild:jsbun build src/index.ts --outdir dist --format esm --target node --external vite --external unified --external remark-parse --external remark-html --external mdast-util-from-markdown --external @leandown/core --external @leandown/remark --external cmd-tsbuild:templatesrm -rf dist/template && cp -r src/template dist/template
Dependencies7
@leandown/coreworkspace:*@leandown/remarkworkspace:*cmd-ts^0.13.0remark^15.0.1remark-html^16.0.1unified^11.0.5vite^6.0.0