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
- zhangfanbin
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
Scripts9
buildtsc -p tsconfig.build.json && chmod +x dist/cli.jsdashboardnpm run --prefix dashboard devdevtsx watch src/index.tsdev:allconcurrently "npm run dev" "npm run dashboard"linteslint src/prepublishOnlynpm run buildstartnode dist/index.jstestvitest runtest:watchvitest
Dependencies14
@ai-sdk/anthropic^1.0.0@ai-sdk/openai^1.0.0ai^4.0.0chokidar^4.0.0cors^2.8.5dotenv^17.4.2express^4.21.0helmet^8.0.0nanoid^5.0.0ollama-ai-provider^1.0.0pino^9.0.0pino-pretty^13.0.0proper-lockfile^4.1.2zod^3.23.0