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
- 33
- First published
- May 2026
- Publisher
- dangbt
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":["@dangbt/[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":["@dangbt/[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
Scripts12
buildtsc -b && vite buildbuild-storybookstorybook buildbuild:libvite build -c vite.lib.config.ts && tsc -p tsconfig.lib.jsoncli:devpnpm --filter create-pro-ui-app devdevvitegen:llmsnode generate-llms-full.mjsgen:registrynode generate-registry.mjsmcp:devpnpm --filter mcp-pro-ui devpreviewvite previewstorybookstorybook dev -p 6006tools:buildpnpm -r --filter './tools/**' buildtools:publishpnpm -r --filter './tools/**' publish --no-git-checks
Dependencies3
clsx2.1.1tailwind-merge2.6.1tailwindcss-react-aria-components2.1.0