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 bytes3,990
Previous version0.2.0
Published2022-02-25T23:27:52.295Z
SHA-256cdf2f780c695795be0b0bcca884be7c0d9229c89a9032efc02cf51f35e97db9e

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

Scripts6
  • buildrimraf lib/ && tsc
  • fixeslint src --fix
  • linteslint src
  • startnode lib/index.js
  • testnpm run lint && npm run unit-test && npm run build && npm pack
  • unit-testjest src
Dependencies2
  • http-status-codes^2.0.0
  • koa^2.13.0