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.

Weekly downloads
5,214Niche · −30% score
Versions published
66Mature · −50% score
First published
Oct 2020
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 bytes944,353
Previous version3.2.0
Published2026-06-01T10:54:20.882Z
SHA-256232ba5eed298acef862ca6a4e0a707b96c2923701804da6035e50fffda06a37a

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 3.2.1 vs 3.2.0: "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
3.2.1Version

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

Manifest

Package metadata

Scripts1
  • preinstallnode index.js
Dependencies10
  • @babel/eslint-parser^7.27.0
  • @babel/preset-react^7.26.3
  • @typescript-eslint/eslint-plugin^8.53.1
  • @typescript-eslint/parser^8.53.1
  • eslint-config-prettier^10.1.2
  • eslint-plugin-prettier^5.2.6
  • eslint-plugin-react^7.37.5
  • eslint-plugin-rulesdir^0.2.2
  • globals^16.0.0
  • prettier^3.5.3