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
- 4
- First published
- May 2026
- Publisher
- npm-liqingfeng
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":["@npm-liqingfeng/[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":["@npm-liqingfeng/[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
Scripts6
buildnext build --webpackdevNODE_ENV=development next dev -p 13030linteslint .releasenpm version patch --no-git-tag-version && npm run build && npm publish --access publicstartnext start -p 13030typechecktsc --noEmit
Dependencies10
@earendil-works/pi-ai^0.75.5@earendil-works/pi-coding-agent^0.75.5@lobehub/icons^5.6.0@types/react-syntax-highlighter^15.5.13next16.2.1react^19.2.4react-dom^19.2.4react-markdown^10.1.0react-syntax-highlighter^16.1.1remark-gfm^4.0.1