@patternfly/pfe-tools
Development and build tools for PatternFly Elements and related projects
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads package.json via normalized path for version lookup; not user-controlled input. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 7.0.0 | 0 / 10 | |
| 6.0.1 | 0 / 10 | |
| 6.0.0 | 0 / 10 | |
| 5.0.5 | 0 / 10 |
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
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.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.