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
- 184
- Versions published
- 37
- First published
- Mar 2026
- Publisher
- braydenyang
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":["@braydenyang/[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":["@braydenyang/[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
buildvue-tsc --noEmit && vite buildbuild:libvue-tsc --noEmit && vite build --mode libdevvite --host 0.0.0.0formatprettier --write "src/**/*.{ts,vue,css,json}"linteslint src --ext .ts,.vuelint:fixeslint src --ext .ts,.vue --fixpreviewvite previewreleasepnpm publish --access public --no-git-checkstype-checkvue-tsc --noEmit
Dependencies6
highlight.js^11.10.0naive-ui^2.40.3pinia^2.2.6vue^3.5.13vue-json-pretty^2.6.0vue-router^4.5.0