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
- 16
- First published
- Mar 2026
- Publisher
- zeekay
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":["@hanzogui/[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":["@hanzogui/[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
Scripts5
buildhanzo-gui-buildcleanhanzo-gui-build cleanclean:buildhanzo-gui-build clean:buildtest:webvitest --typecheck --runwatchhanzo-gui-build --watch
Dependencies11
@hanzogui/compose-refs4.4.0@hanzogui/constants4.4.0@hanzogui/helpers4.4.0@hanzogui/is-equal-shallow4.4.0@hanzogui/native4.4.0@hanzogui/normalize-css-color4.4.0@hanzogui/timer4.4.0@hanzogui/types4.4.0@hanzogui/use-did-finish-ssr4.4.0@hanzogui/use-event4.4.0@hanzogui/use-force-update4.4.0