@rh-support/utils
> TODO: description
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Red Hat internal package with long history; maintainer additions are routine org operations. | ai | |
| provenance | no-provenance | AI (provenance): Established Red Hat internal utility package; provenance absence is consistent across all 375 versions. | ai | |
| dependencies | unvetted-dep:@cee-eng/hydrajs | AI (dependencies): Internal Red Hat library from cee.redhat.com; consistent with this package's origin and stable across versions. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.5.92 | 10 / 9 | |
| 2.5.85 | 10 / 9 | |
| 2.5.82 | 10 / 9 | |
| 2.5.81 | 10 / 9 | |
| 2.5.69 | 10 / 9 | |
| 2.5.59 | 10 / 9 | |
| 2.5.52 | 10 / 9 | |
| 2.5.44 | 10 / 9 | |
| 2.5.28 | 10 / 9 | |
| 2.5.27 | 10 / 9 | |
| 2.5.24 | 10 / 9 | |
| 2.5.23 | 10 / 9 | |
| 2.5.19 | 10 / 9 | |
| 2.5.18 | 10 / 9 | |
| 2.5.14 | 10 / 9 | |
| 2.5.12 | 10 / 9 |
v2.5.92
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bkale) than the most recent previously approved version (anujsi) on 2026-06-04, but bkale is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.5.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.