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
367Mature · −50% score
First published
May 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 bytes987,241
Previous version6.11.2
Published2026-06-01T10:54:36.562Z
SHA-2562624c8e1e465371132258a8c48e63750f6c1d8e01423a996ea4dc54d6cad81dd

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 6.11.3 vs 6.11.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
6.11.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 6.11.3 vs 6.11.2: "node index.js"40
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpreinstall added in 6.11.3 vs 6.11.2: "node index.js"40
lowInstall-time lifecycle scriptpackage.jsonpreinstall="node index.js"5
lowLarge Javascript Payloadpackage/index.js4294798 bytes0

Manifest

Package metadata

Scripts1
  • preinstallnode index.js
Dependencies44
  • @pmmmwh/react-refresh-webpack-plugin^0.5.15
  • @redhat-cloud-services/frontend-components-config-utilities^4.9.0
  • @redhat-cloud-services/tsc-transform-imports^1.0.26
  • @sentry/webpack-plugin^4.5.0
  • @swc/core^1.3.76
  • assert^2.0.0
  • axios^1.12.2
  • browserify-zlib^0.2.0
  • buffer^6.0.3
  • chalk^4.1.2
  • clean-webpack-plugin^4.0.0
  • concurrently^7.4.0
  • css-loader^5.2.7
  • express^4.19.2
  • fork-ts-checker-webpack-plugin^9.0.2
  • git-revision-webpack-plugin^5.0.0
  • glob^7.2.3
  • html-replace-webpack-plugin^2.6.0
  • html-webpack-plugin^5.5.0
  • http-server^14.0.0
  • https-proxy-agent^5.0.1
  • inquirer^8.2.4
  • js-yaml^4.1.0
  • jsonc-parser^3.3.1
  • jws^4.0.0
  • lodash^4.17.21
  • mini-css-extract-plugin^2.9.1
  • path-browserify^1.0.1
  • process^0.11.10
  • react-refresh^0.14.0
  • …and 14 more.