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
- 117
- Versions published
- 2
- First published
- Jun 2026
- Publisher
- harlanwang
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
Scripts16
buildnode scripts/update-build-version.js && vue-tsc --noEmit && vite buildbuild:typesvue-tsc --declaration --emitDeclarationOnly --outDir distcheckvue-tsc --noEmitdevvite --config docs/vite.config.tsdev:libvite build --watchdocs:buildvite build --config docs/vite.config.tsdocs:devvite --config docs/vite.config.tsdocs:previewvite preview --config docs/vite.config.ts --outDir dist-docslogin:npmnpm login --registry=https://registry.npmjs.org/prepack:checknode scripts/check-package-files.jsprepublishOnlynpm run buildpreviewvite previewpublish:betanpm config set registry https://registry.npmjs.org & npm publish --tag beta & npm config set registry https://registry.npmmirror.compublish:npmnpm publish --registry=https://registry.npmjs.org/ --access publicpublish:releasenpm config set registry https://registry.npmjs.org & npm run publish:npm & npm config set registry https://registry.npmmirror.comupdate-buildnode scripts/update-build-version.js
Dependencies5
@iconify/vue^5.0.0@unocss/preset-wind3^66.5.7@vueuse/core^11.0.0dayjs^1.11.13lodash-es^4.17.21