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
- 317
- Versions published
- 79
- First published
- Feb 2026
- Publisher
- payez_jon
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":["@payez/[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":["@payez/[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
buildnpx tsc --project tsconfig.jsondevnext devdev:brokerpwsh -NoProfile -ExecutionPolicy Bypass -File scripts/dev-broker.ps1dev:localpwsh -NoProfile -ExecutionPolicy Bypass -File scripts/dev-local.ps1prepublishOnlynpm run build
Dependencies12
@azure/identity^4.0.1@azure/keyvault-secrets^4.7.0@better-auth/memory-adapter^1.5.6@upstash/redis^1.35.6better-auth^1.5.6ioredis^5.3.2jose^5.2.4jsonwebtoken^9.0.2jwk-to-pem^2.0.5jwt-decode^4.0.0lodash^4.17.21nanoid^5.0.7