@csstools/postcss-color-function-display-p3-linear
Use the display-p3-linear color space on the color() function in CSS
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 |
|---|---|---|---|---|
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a well-known permissive license (MIT without attribution). Used consistently across the csstools org; not a risk. | ai | |
| phantom-deps | phantom-dep:@csstools/utilities | AI (phantom-deps): Same-org dependency in a monorepo context; explicit declaration is a common pattern for version management in PostCSS plugin ecosystems. | ai | |
| phantom-deps | phantom-dep:@csstools/css-tokenizer | AI (phantom-deps): Same-org transitive dependency declared explicitly; standard monorepo practice for the csstools PostCSS plugins. | ai | |
| phantom-deps | phantom-dep:@csstools/css-color-parser | AI (phantom-deps): Same-org transitive dependency declared explicitly; standard monorepo practice for the csstools PostCSS plugins. | ai | |
| phantom-deps | phantom-dep:@csstools/css-parser-algorithms | AI (phantom-deps): Same-org transitive dependency declared explicitly; standard monorepo practice for the csstools PostCSS plugins. | ai | |
| phantom-deps | phantom-dep:@csstools/postcss-progressive-custom-properties | AI (phantom-deps): Same-org transitive dependency declared explicitly; standard monorepo practice for the csstools PostCSS plugins. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.4 | 5 / 0 | |
| 2.0.3 | 5 / 0 | |
| 2.0.2 | 5 / 0 | |
| 2.0.1 | 5 / 0 | |
| 2.0.0 | 5 / 0 | |
| 1.0.1 | 5 / 0 | |
| 1.0.0 | 5 / 0 |
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.