postcss
Tool for transforming styles with JS plugins
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:source-map-js | AI (dependencies): source-map-js is a well-known Mozilla source-map fork used throughout the JS/CSS tooling ecosystem; its use in postcss for source map support is expected and appropriate. | ai | |
| provenance | no-provenance | AI (provenance): postcss is a long-established package (4550 days); lack of Sigstore provenance is common and not a risk signal for this well-known project. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is a legitimate feature for parsing source maps embedded in CSS; no malicious payload risk in this context. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 8.5.15 | 3 / 0 | |
| 8.5.14 | 3 / 0 | |
| 8.5.13 | 3 / 0 | |
| 8.5.12 | 3 / 0 | |
| 8.5.11 | 3 / 0 | |
| 8.5.10 | 3 / 0 | |
| 8.5.9 | 3 / 0 | |
| 8.5.8 | 3 / 0 | |
| 8.5.7 | 3 / 0 | |
| 8.5.6 | 3 / 0 | |
| 8.5.5 | 3 / 0 | |
| 8.5.4 | 3 / 0 | |
| 8.5.3 | 3 / 0 | |
| 8.5.2 | 3 / 0 | |
| 8.5.1 | 3 / 0 | |
| 8.5.0 | 3 / 0 | |
| 8.4.49 | 3 / 0 | |
| 8.4.48 | 3 / 0 | |
| 8.4.47 | 3 / 0 | |
| 8.4.46 | 3 / 0 | |
| 8.4.45 | 3 / 0 | |
| 8.4.44 | 3 / 0 | |
| 8.4.43 | 3 / 0 | |
| 8.4.42 | 3 / 0 | |
| 8.4.41 | 3 / 0 | |
| 8.4.40 | 3 / 0 | |
| 8.4.39 | 3 / 0 | |
| 8.4.38 | 3 / 0 | |
| 8.4.37 | 3 / 0 | |
| 8.4.36 | 3 / 0 | |
| 8.4.35 | 3 / 0 | |
| 8.4.34 | 3 / 0 | |
| 8.4.33 | 3 / 0 | |
| 8.4.32 | 3 / 0 | |
| 8.4.31 | 3 / 0 |
v8.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.