PkgRadar

Package evidence

@redocly/[email protected]

no findings

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Versions published
2
First published
May 2026
Publisher
romanhotsiy

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":["@redocly/[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":["@redocly/[email protected]"],"fail_on":"review"}'
Publisherromanhotsiy
Artifact bytes12,600
Previous version1.3.0
Published2026-05-28T15:36:45.178Z
SHA-256a87743b2ee1ecf8e1577a238cddca2b7c923df4e84181da80cf1daeb415f79eb

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.3.1Version
Status history (2 events)
  1. new → available · risk low · score 0 · status changed
  2. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • buildmicrobundle --format cjs --no-compress --inline none src/*.js
  • devkarmatic watch --no-headless
  • prepublishOnlynpm run build
  • releasenpm t && git commit -am $npm_package_version && git tag $npm_package_version && git push && git push --tags && npm publish
  • testnpm run build && karmatic && NODE_ENV=production karmatic -p
Dependencies1
  • loader-utils^2.0.0