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
- 273
- Versions published
- 9
- First published
- Apr 2026
- Publisher
- baditu20
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
buildrollup -c rollup.config.js && node scripts/write-bin.jschangeset:releaseyarn build && changeset publishclinode bin/create-scaffold-hbar.jsdevrollup -c rollup.config.js --watchformatprettier --write .linteslint .testvitest runtest:coveragevitest run --coveragetest:watchvitesttype-checktsc --noEmit
Dependencies11
@clack/prompts^0.9.0chalk^5.4.1commander^12.1.0execa^9.6.0figlet^1.8.0fs-extra^11.3.0giget^1.2.3listr2^9.0.1semver^7.7.2validate-npm-package-name^6.0.1zod^3.24.1