@redhat-cloud-services/chromenpm
This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →- latest 2.4.14
- last known licence Apache-2.0
- stars 39
- assessment attempted today
- GitHub evidence observed today
- registry checked 26 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 11 checks
What the project says about itself
- Build provenance — the latest release, 2.4.14, carries a signed provenance attestation. Source: the registry.
- Publishers on the registry — 4. Source: the registry.
- Security policy — published. Source: the repository.
- OpenSSF Scorecard — 5.3 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked today; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-12 | first verdict: active |
Supply-chain history 1
-
account hijacked 2026-06 2.3.1, 2.3.2
A compromised employee GitHub account pushed orphan commits with a rogue workflow that abused trusted publishing to release versions carrying a credential-stealing worm.
Removed; users were told to rotate every CI and cloud credential touched since the start of June.
Source: Aikido analysis, 1 June 2026. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/@redhat-cloud-services/chrome)Watch it
Get told when @redhat-cloud-services/chrome changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.