@patternfly/patternfly
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/icons/pficons.mjs | AI (source-diff): Minified SVG icon data bundle; long lines are SVG path data, not obfuscated malicious code. Stable pattern for this package. | ai | |
| provenance | publisher-changed | AI (provenance): dlabaj is an established contributor with 3 approved packages; transition from patternfly-build org account is consistent with normal maintainer rotation. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 6.5.2 | 0 / 67 | |
| 6.5.1 | 0 / 67 | |
| 6.5.0 | 0 / 67 | |
| 6.4.0 | 0 / 62 |
v6.5.2
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.
v6.5.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dlabaj) than the most recent previously approved version (patternfly-build) on 2026-05-21, but dlabaj 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.
v6.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dlabaj) than the most recent previously approved version (patternfly-build) on 2026-05-20, but dlabaj 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.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.