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
- 1
- First published
- Jun 2026
- Publisher
- laomai_codefee
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
Scripts7
buildvue-tsc --noEmit && vite buildbuild:demovite build --mode demodevvite --mode demo --openpreviewvite preview --mode demotestvitest runtest:coveragevitest run --coveragetest:watchvitest
Dependencies18
@floating-ui/dom^1.7.4@vueuse/core^10.11.0class-variance-authority^0.7.0clsx^2.1.1exceljs^4.4.0file-saver^2.0.5konva^9.3.14lucide-vue-next^0.344.0nanoid^5.1.6pdf-lib^1.17.1pdfjs-dist~4.3.136pinia^2.1.7radix-vue^1.9.0tailwind-merge^2.3.0tailwindcss-animate^1.0.7vue^3.5.0vue-i18n^10.0.0web-highlighter^0.7.4