PkgRadar

Package evidence

@redhat-cloud-services/[email protected]

Install-time lifecycle script: preinstall="node index.js"

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
169Mature · −50% score
First published
Mar 2019
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

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":["@redhat-cloud-services/[email protected]"],"fail_on":"high"}'

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":["@redhat-cloud-services/[email protected]"],"fail_on":"high"}'
Artifact bytes1,068,348
Previous version5.0.2
Published2026-06-01T10:55:09.501Z
SHA-25648555580b8d831dd04679b2e97b0c447e2d66970792ccae4c193c4b300fb48d4

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 5.0.3 vs 5.0.2: "node index.js"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

not present

status
Last checked
noneRisk
Score
5.0.3Version

Latest scanner note: @redhat-cloud-services/[email protected] not present in registry metadata

Status history (2 events)
  1. availablenot_present · risk none · score · @redhat-cloud-services/[email protected] not present in registry metadata
  2. newavailable · risk high · score 45 · status changed

Evidence

Static findings

2 static · 1 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 5.0.3 vs 5.0.2: "node index.js"40
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 5.0.3 vs 5.0.2: "node index.js"40
lowInstall-time lifecycle scriptpackage.jsonpreinstall="node index.js"5
lowLarge Javascript Payloadpackage/index.js4294888 bytes0

Manifest

Package metadata

Scripts2
  • doctypedoc
  • preinstallnode index.js
Dependencies2
  • @redhat-cloud-services/javascript-clients-shared^2.0.5
  • tslib^2.6.2