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
- 512
- Versions published
- 86
- First published
- May 2026
- Publisher
- dom082186
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
Scripts9
buildnpm run clean && tsc -p tsconfig.build.json && vite buildbuild-storybookstorybook buildcheck:iconsnode ./scripts/check-icons-duplicates.mjscheck:typesvue-tsc --noEmit -p tsconfig.app.json && tsc -p tsconfig.build.json --noEmitcheck:verifynpm run check:types && npm run buildcleannode -e "import('node:fs').then(({rmSync}) => rmSync('dist', { recursive: true, force: true }))"devvitepreviewvite previewstorybookstorybook dev -p 6006
Dependencies5
@floating-ui/dom^1.7.4@vueuse/core^14.3.0dayjs^1.11.20lodash^4.18.1zod^4.4.3