@csstools/postcss-color-mix-variadic-function-arguments
Mix any number of colors with the color-mix 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@csstools/utilities | AI (phantom-deps): Same-org @csstools dep declared in package.json but used transitively; consistent pattern across csstools monorepo plugins. | ai | |
| phantom-deps | phantom-dep:@csstools/css-tokenizer | AI (phantom-deps): Same-org @csstools dep; transitive usage pattern is expected in csstools plugin ecosystem. | ai | |
| phantom-deps | phantom-dep:@csstools/css-color-parser | AI (phantom-deps): Same-org @csstools dep; transitive usage pattern is expected in csstools plugin ecosystem. | ai | |
| phantom-deps | phantom-dep:@csstools/css-parser-algorithms | AI (phantom-deps): Same-org @csstools dep; transitive usage pattern is expected in csstools plugin ecosystem. | ai | |
| phantom-deps | phantom-dep:@csstools/postcss-progressive-custom-properties | AI (phantom-deps): Same-org @csstools dep; transitive usage pattern is expected in csstools plugin ecosystem. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a well-known permissive license (MIT without attribution requirement); csstools uses it consistently across their packages. | ai |
Versions (showing 8 of 8)
| 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.2 | 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.