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
- 2
- First published
- Jun 2026
- Publisher
- lonewolfyx
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
Scripts10
buildnuxt build && tsdown && rimraf ./dist/nitro.jsondevnuxt devdev:clitsdown -wgeneratenuxt generatelintnuxt prepare && eslint .lint:fixnuxt prepare && eslint --fixpreparesimple-git-hooksprepublishOnlypnpm buildpreviewnuxt previewtypechecknuxt typecheck
Dependencies12
@clack/prompts^1.5.1@lucide/vue^1.17.0@tanstack/vue-virtual^3.13.29cac^7.0.0class-variance-authority^0.7.1clsx^2.1.1dayjs^1.11.21glob^13.0.6reka-ui^2.7.0vaul-vue^0.4.1vue^3.5.26vue-router^4.6.4