PkgRadar

Package evidence

@legna-lnc/[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":["@legna-lnc/[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":["@legna-lnc/[email protected]"],"fail_on":"review"}'
Publisherlegnaee
Artifact bytes48,592,812
Previous version2.1.7
Published2026-05-25T06:29:41.949Z
SHA-2569177055facbf2b4aac8cebf72df5659399229a3921085c08a986e956374c2848

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
2.1.8Version
Status history (2 events)
  1. scan_error → available · risk low · score 0 · status scan_error -> available, risk none -> low, score none -> 0
  2. new → scan_error · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@legna-lnc/legnacode-win32-ia32/-/legnacode-win32-ia32-2.1.8.tgz)

Evidence

Static findings

No findings stored for this release.