@patternfly/react-docs
PatternFly React Docs
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): dlabaj is a known PatternFly/Red Hat contributor with 3 prior approvals; transition appears legitimate within the org. | ai | |
| dependencies | unvetted-dep:victory | AI (dependencies): victory is a well-known charting library used by PatternFly react-charts; stable dependency for this package. | ai | |
| typosquat | typosquat.levenshtein:react-dom | AI (typosquat): Scoped @patternfly org package; not a typosquat of react-dom, just Levenshtein proximity. | ai | |
| phantom-deps | phantom-dep:echarts | AI (phantom-deps): Docs package; echarts referenced in config for optional chart examples, not a direct import. | ai | |
| phantom-deps | phantom-dep:victory | AI (phantom-deps): Docs package; victory referenced in config for chart examples, not a direct import. | ai | |
| phantom-deps | phantom-dep:@patternfly/react-code-editor | AI (phantom-deps): Same-org dep used in docs examples via config; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 7.5.1 | 12 / 2 | |
| 7.5.0 | 12 / 2 | |
| 7.4.3 | 12 / 2 | |
| 7.4.2 | 12 / 2 | |
| 7.4.1 | 12 / 2 | |
| 7.4.0 | 12 / 2 | |
| 7.3.1 | 12 / 2 | |
| 7.3.0 | 12 / 2 | |
| 7.2.3 | 12 / 2 |
v7.5.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v7.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. 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.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.