@patternfly/react-styles
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
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 contributor with 6 approved packages; transition from CI bot account to personal account is plausible for this org. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.6.0 | 0 / 3 | |
| 6.5.1 | 0 / 3 | |
| 6.5.0 | 0 / 3 | |
| 6.4.0 | 0 / 3 | |
| 6.3.1 | 0 / 3 | |
| 6.3.0 | 0 / 3 | |
| 6.2.2 | 0 / 3 | |
| 6.2.1 | 0 / 3 | |
| 6.2.0 | 0 / 3 | |
| 6.1.0 | 0 / 3 | |
| 6.0.0 | 0 / 3 |
v6.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.