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":["@rzl-zone/[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":["@rzl-zone/[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
Scripts6
buildtsdowncheck-publishpnpm build && pnpm pack --dry-runcheck-types:packagetsc --noEmitdev:packagetsdown --watch "./src/**/*"linteslintrelease-patchpnpm version patch && git push && git push --tags && pnpm publish
Dependencies9
@edge-runtime/cookies^6.0.0@rzl-zone/core0.0.12-beta.0@rzl-zone/core-react0.0.12-beta.0@rzl-zone/node-only0.0.11-beta.0@rzl-zone/ts-types-plus0.1.8-beta.0@rzl-zone/utils-js3.14.0-beta.0deepmerge^4.3.1p-safe^1.1.0validate-color^2.2.4