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
- 1
- First published
- Jun 2026
- Publisher
- peterfei
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
buildtsup src/cli.ts --format esm --target node18 --out-dir dist --clean --external @mermaid-js/mermaid-cli --external puppeteerdevtsup src/cli.ts --format esm --target node18 --out-dir dist --watchprepublishOnlynpm run buildtestvitest runtest:watchvitest
Dependencies11
chalk^5.3.0commander^12.0.0tree-sitter^0.25.0tree-sitter-c^0.24.1tree-sitter-cpp^0.23.4tree-sitter-go^0.25.0tree-sitter-java^0.23.5tree-sitter-javascript^0.25.0tree-sitter-python^0.25.0tree-sitter-rust^0.24.0tree-sitter-typescript^0.23.2
Optional dependencies1
@mermaid-js/mermaid-cli^11.15.0