@rh-support/react-context
## Usage
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): Established Red Hat org package; maintainer additions are routine team changes, no code or script changes accompany this version. | ai | |
| provenance | publisher-changed | AI (provenance): arajak is an established Red Hat publisher with 47 approved packages; transition appears legitimate within the rh-support org. | ai | |
| provenance | no-provenance | AI (provenance): Internal Red Hat monorepo package; provenance via Sigstore CI/CD not configured for this org's pipeline. | ai | |
| dependencies | unvetted-dep:@cee-eng/hydrajs | AI (dependencies): Internal Red Hat/CEE engineering library; consistent with package's Red Hat origin and present across many versions. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared as peer/dep for React app context; referenced in config files only, not a real phantom dep issue for this package. | ai | |
| phantom-deps | phantom-dep:react-test-renderer | AI (phantom-deps): Test renderer declared as peer dep; config-file reference only, stable false positive. | ai | |
| phantom-deps | phantom-dep:react-router-dom | AI (phantom-deps): Same pattern — config-file reference only; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.5.254 | 15 / 14 | |
| 2.5.125 | 15 / 14 | |
| 2.5.117 | 15 / 14 | |
| 2.5.94 | 15 / 14 | |
| 2.5.93 | 15 / 14 | |
| 2.5.78 | 15 / 14 | |
| 2.5.74 | 15 / 14 | |
| 2.5.70 | 15 / 14 | |
| 2.5.21 | 15 / 14 | |
| 2.5.20 | 15 / 14 |
v2.5.254
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 (arajak) 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.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.74
2 findingsThis version was published by a different npm account than previous versions on 2025-10-27. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.