PkgRadar

Package evidence

@howdygo/[email protected]

no findings

Recommended action

Looks clean — keep monitoring

No 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":["@howdygo/[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":["@howdygo/[email protected]"],"fail_on":"review"}'
Publisherhowdygo
Artifact bytes9,864
Previous version2.0.0-alpha.43
Published2026-03-16T02:49:05.796Z
SHA-256cf09a3797f0df9ce65c7862bb896f5e9f8b5742ef845e1639dbbb00cc16aaad7

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

low
Last checked
lowRisk
0Score
2.0.0-alpha.44Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • buildtsc -noEmit && vite build
  • check-typestsc -noEmit
  • devvite build --watch
  • lintyarn eslint src/**/*.ts
  • prepublishnpm run build