PkgRadar

Package evidence

@cms0/[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.

Inspect tarballAdd to CI gate
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":["@cms0/[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":["@cms0/[email protected]"],"fail_on":"review"}'
Publisherjeffrey0606
Artifact bytes18,329
Previous version0.2.25
Published2026-05-24T05:16:10.903Z
SHA-2566afdbf38e2924bf797b693f32856e66c1bb7b322cc7e8150941b5cb77565400c

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
0.2.26Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts6
  • buildpnpm run build:clean && tsc -p tsconfig.json
  • build:cleannode -e "require('fs').rmSync('dist', { recursive: true, force: true });"
  • linttsc -p tsconfig.json --noEmit
  • testpnpm test:unit
  • test:unitpnpm -C ../.. exec vitest run --config vitest.config.ts --project shared-unit
  • typechecktsc -p tsconfig.json --noEmit
Dependencies1
  • zod^4.1.12