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
- 22
- First published
- Feb 2026
- Publisher
- docthub.ui
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
Scripts13
buildvite build && tsc --build tsconfig.build.json --force && tsc-alias -p tsconfig.build.jsonbuild-storybookstorybook buildcheckbiome check .check:fixbiome check --write .devviteformatbiome format --write .lintbiome lint .lint:biomebiome lint .preparehuskyprepublishOnlynpm run buildpreviewvite previewstorybookstorybook dev -p 6006type-checktsc --noEmit
Dependencies10
clsx^2.1.1dayjs^1.11.19docthub-core-components2.99.0react^19.0.0react-dom^19.0.0react-hook-form^7.50.0react-icons^5.5.0react-phone-number-input^3.4.14react-router-dom^7.13.0zod^4.0.0