rollup-plugin-postcss
Seamless integration between Rollup and PostCSS
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): Publisher changed to egoist who is the repo owner and listed author; this is the canonical maintainer, not a takeover. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): chalk is declared in dependencies and used at runtime; analyzer trace miss is a false positive. | ai |
Versions (showing 86 of 86)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 13 / 16 | |
| 4.0.1 | 13 / 16 | |
| 4.0.0 | 13 / 16 | |
| 3.1.8 | 14 / 15 | |
| 3.1.7 | 14 / 15 | |
| 3.1.6 | 14 / 15 | |
| 3.1.5 | 14 / 15 | |
| 3.1.4 | 14 / 15 | |
| 3.1.3 | 14 / 15 | |
| 3.1.2 | 14 / 15 | |
| 3.1.1 | 14 / 15 | |
| 3.1.0 | 14 / 15 | |
| 3.0.0 | 14 / 15 | |
| 2.9.0 | 14 / 15 | |
| 2.8.2 | 14 / 15 | |
| 2.8.1 | 14 / 15 | |
| 2.6.4 | 14 / 15 | |
| 2.6.2 | 14 / 15 | |
| 2.6.1 | 14 / 15 | |
| 2.5.0 | 14 / 14 | |
| 2.4.1 | 14 / 14 | |
| 2.4.0 | 14 / 14 | |
| 2.3.0 | 14 / 14 | |
| 2.2.0 | 14 / 14 | |
| 2.1.1 | 14 / 14 | |
| 2.0.6 | 14 / 14 | |
| 2.0.5 | 14 / 14 | |
| 2.0.4 | 14 / 14 | |
| 2.0.3 | 14 / 13 | |
| 2.0.2 | 14 / 13 | |
| 2.0.1 | 14 / 15 | |
| 2.0.0 | 14 / 15 | |
| 1.6.3 | 15 / 12 | |
| 1.6.2 | 16 / 12 | |
| 1.6.1 | 15 / 12 | |
| 1.6.0 | 15 / 12 | |
| 1.5.1 | 15 / 12 | |
| 1.5.0 | 15 / 12 | |
| 1.4.1 | 14 / 12 | |
| 1.4.0 | 14 / 12 | |
| 1.3.4 | 14 / 12 | |
| 1.3.3 | 13 / 12 | |
| 1.3.2 | 13 / 12 | |
| 1.3.1 | 13 / 12 | |
| 1.3.0 | 13 / 12 | |
| 1.2.9 | 12 / 12 | |
| 1.2.8 | 12 / 12 | |
| 1.2.7 | 12 / 12 | |
| 1.2.6 | 12 / 12 | |
| 1.2.5 | 12 / 12 | |
| 1.2.4 | 12 / 12 | |
| 1.2.3 | 12 / 12 | |
| 1.2.2 | 12 / 12 | |
| 1.2.1 | 12 / 12 | |
| 1.2.0 | 12 / 12 | |
| 1.1.0 | 12 / 12 | |
| 1.0.5 | 12 / 10 | |
| 1.0.4 | 12 / 10 | |
| 1.0.3 | 12 / 10 | |
| 1.0.2 | 12 / 9 | |
| 1.0.1 | 12 / 9 | |
| 1.0.0 | 11 / 9 | |
| 0.5.6 | 7 / 18 | |
| 0.5.5 | 7 / 18 | |
| 0.5.4 | 7 / 18 | |
| 0.5.3 | 7 / 18 | |
| 0.5.2 | 7 / 18 | |
| 0.5.1 | 5 / 18 | |
| 0.5.0 | 5 / 17 | |
| 0.4.3 | 5 / 17 | |
| 0.4.1 | 5 / 17 | |
| 0.4.0 | 5 / 17 | |
| 0.3.1 | 5 / 16 | |
| 0.2.0 | 3 / 11 | |
| 0.1.1 | 3 / 10 | |
| 0.1.0 | 3 / 10 | |
| 0.0.27 | 3 / 10 | |
| 0.0.26 | 3 / 10 | |
| 0.0.25 | 3 / 10 | |
| 0.0.24 | 3 / 10 | |
| 0.0.23 | 3 / 10 | |
| 0.0.22 | 3 / 10 | |
| 0.0.21 | 3 / 10 | |
| 0.0.11 | 2 / 9 | |
| 0.0.2 | 3 / 10 | |
| 0.0.1 | 2 / 9 |
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2020-04-23. 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.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.