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.
- Weekly downloads
- 420
- Versions published
- 47
- First published
- Mar 2026
- Publisher
- wangyang1103
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":["@deppon/[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":["@deppon/[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
buildrimraf lib && rollup -c ./rollup.config.mjsdevrollup -w -c rollup.config.mjsformatprettier --write **/*.{js,ts} && eslint . --ext js,ts --fixlinteslint . --ext js,ts,tsxprePublishnpm run build && npm publishpublish:autonpm publish
Dependencies17
@deppon/deppon-monitor-browser2.5.12@unocss/postcss0.51.12@vitejs/plugin-vue^5.0.0autoprefixer^10.4.20chalk^4.1.0chokidar3.5.3dotenv8.2.0dotenv-expand5.1.0fs-extra8.1.0less^4.2.0open^8.4.2postcss8.4.12ts-node^10.8.1tsx^4.7.0unocss0.51.12vite^5.0.0vue^3.3.4