PkgRadar

Package evidence

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

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":["@edular/[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":["@edular/[email protected]"],"fail_on":"review"}'
Publisherklassapp
Artifact bytes9,551
Previous version5.2.1
Published2026-05-25T04:54:13.670Z
SHA-2562509a8dcd830ceed621249138ee349b2bd8d6ea150b01bb97b34f496440b6fdc

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
5.2.2Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • buildtsc
  • build:cleanrm -rf lib
  • generate-modulests-node scripts/generate-modules.ts
  • prepublishyarn build:clean && yarn build
  • testyarn build:clean && yarn build && node lib/test.js
Dependencies2
  • axios^0.26.1
  • dotenv^16.0.3