postcss-color-hwb
PostCSS plugin to transform W3C CSS hwb() color to more compatible CSS (rgb() (or rgba()))
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): Legitimate maintainer transition within the postcss ecosystem in 2017; semigradsky is a well-established publisher with 122 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jonathantneal and semigradsky are known postcss ecosystem contributors; legitimate maintainer addition. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; common for packages from this era. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 4 / 3 | |
| 2.0.1 | 4 / 4 | |
| 2.0.0 | 4 / 3 | |
| 1.2.0 | 4 / 3 | |
| 1.1.0 | 3 / 4 | |
| 1.0.0 | 2 / 4 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2017-05-15. 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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.