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 bytes547,667
Previous version2022.2.0
Published2022-11-02T18:56:03.447Z
SHA-256d3554d6c54d620c6515164194a8e6ca249b5f9d41ccecf3fadd02fbf6acf11d8

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
2022.11.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

Scripts8
  • buildrm -rf lib/ && tsc && ./write-git-info.sh
  • devnodemon --exec bash -c 'npm run build && npm run start' --watch src --ext ts,tsx
  • linteslint --ext .ts,.tsx src
  • lint:fixnpm run lint -- --fix
  • releasecarnesen-dev release --semverBump date
  • startnode lib
  • testnpm run lint && npm run unit-test && npm run build
  • unit-testjest src
Dependencies5
  • http-status-codes2.2.0
  • koa2.13.4
  • koa-static5.0.0
  • react17.0.2
  • react-dom17.0.2