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
- 6
- First published
- Jan 2024
- Publisher
- qiwa
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":["@bty/[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":["@bty/[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
Scripts4
buildrm -rf dist && node build.mjsdevnode build.mjs --watchlinteslint src/publish-packagespnpm build && changeset version && changeset publish --access=public --registry=https://bty-reg.bantouyan.com/repository/bty/bty-npm/
Dependencies12
@radix-ui/react-avatar^1.0.3@radix-ui/react-label^2.0.2@radix-ui/react-slot^1.0.2@sindresorhus/is^6.1.0@vanilla-extract/css^1.14.0@vanilla-extract/dynamic^2.1.0@vanilla-extract/recipes^0.5.1antd-mobile^5.33.1clsx^2.0.0copy-to-clipboard^3.3.3react-hook-form^7.45.4react-json-view^1.21.3