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
- 187
- First published
- Feb 2026
- Publisher
- jojo_dio
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":["@dazhicheng/[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":["@dazhicheng/[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
buildrimraf dist && vite buildbuild:analyzerimraf dist && vite build --mode analyzedevvite build --watch --mode developmentdocs:devvite build --watch --mode development
Dependencies13
@dazhicheng/hooks1.4.39@dazhicheng/utils1.3.38@iconify/vue^5.0.0@standard-schema/spec1.0.0@standard-schema/utils0.3.0@tanstack/vue-store^0.8.0@vee-validate/zod^4.15.1es-toolkit^1.45.1numeral^2.0.6pinyin-pro^3.28.1sortablejs^1.15.7vee-validate^4.15.1zod^4.3.6