postcss-value-parser
Transforms css values and at-rule params into the tree
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): evilebottnawi is a known PostCSS ecosystem maintainer; legitimate transition from trysound within the same project community. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 0 / 6 | |
| 4.1.0 | 0 / 6 | |
| 4.0.3 | 0 / 6 | |
| 4.0.2 | 0 / 6 | |
| 4.0.1 | 0 / 6 | |
| 4.0.0 | 0 / 6 | |
| 3.3.1 | 0 / 6 | |
| 3.3.0 | 0 / 4 | |
| 3.2.3 | 0 / 3 | |
| 3.2.1 | 0 / 3 | |
| 3.2.0 | 0 / 3 | |
| 3.1.3 | 0 / 3 | |
| 3.1.2 | 0 / 3 | |
| 3.1.1 | 0 / 3 | |
| 3.1.0 | 0 / 3 | |
| 3.0.3 | 0 / 3 | |
| 3.0.2 | 0 / 3 | |
| 3.0.1 | 0 / 3 | |
| 3.0.0 | 0 / 3 | |
| 2.0.5 | 0 / 3 | |
| 2.0.4 | 0 / 3 | |
| 2.0.3 | 0 / 3 | |
| 2.0.2 | 0 / 3 | |
| 2.0.1 | 0 / 2 | |
| 2.0.0 | 0 / 2 | |
| 1.4.2 | 0 / 2 | |
| 1.4.1 | 0 / 2 | |
| 1.4.0 | 0 / 2 | |
| 1.3.0 | 0 / 2 | |
| 1.2.2 | 0 / 2 | |
| 1.2.1 | 0 / 2 | |
| 1.2.0 | 0 / 2 | |
| 1.1.0 | 0 / 2 | |
| 1.0.2 | 0 / 2 | |
| 1.0.1 | 0 / 2 | |
| 1.0.0 | 0 / 2 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.3.1
2 findingsThis version was published by a different npm account than previous versions on 2018-10-12. 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.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage 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.