PkgRadar

Package evidence

@carnesen/[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":["@carnesen/[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":["@carnesen/[email protected]"],"fail_on":"review"}'
Publishercarnesen
Artifact bytes26,077
Previous version0.11.0
Published2024-05-03T20:58:40.038Z
SHA-256fd7361c41ef472c144370b2be404e9c8e58f40abc2565cb92496dcab32015e77

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
1.0.0Version
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

Scripts9
  • build./scripts/build.sh
  • examplesSTRICT=1 ts-node src/examples.ts
  • linteslint --ext .ts src
  • lint:fixnpm run lint -- --fix
  • releasecarnesen-dev release --semverBump
  • startnode lib
  • test./scripts/test.sh
  • unit-testjest src --coverage
  • unit-test:watchnpm run unit-test -- --watch