@wordpress/global-styles-ui
Global Styles UI components for WordPress.
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:src/font-library/lib/unbrotli.js | AI (source-diff): Base64-encoded Brotli dictionary binary; standard asset for brotli decompression, not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): change-case is a declared runtime dep used in build output; phantom-dep heuristic misfires for bundled packages. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): CSS-only dependency from same org; not imported in JS but legitimately declared for stylesheet builds. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 19 / 0 | |
| 1.14.1 | 19 / 0 | |
| 1.14.0 | 19 / 0 | |
| 1.13.0 | 19 / 0 | |
| 1.12.0 | 19 / 0 | |
| 1.11.0 | 19 / 0 | |
| 1.10.0 | 19 / 0 | |
| 1.9.0 | 19 / 0 | |
| 1.8.0 | 19 / 0 | |
| 1.7.1 | 19 / 0 | |
| 1.7.0 | 19 / 0 | |
| 1.6.0 | 19 / 0 | |
| 1.5.0 | 19 / 0 | |
| 1.4.0 | 19 / 0 | |
| 1.3.0 | 19 / 0 | |
| 1.2.0 | 19 / 0 | |
| 1.1.0 | 19 / 0 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.