postcss-lab-function
Use lab() and lch() color functions 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): First-party @csstools scoped dep declared in package.json; phantom flag is a monorepo artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/css-tokenizer | AI (phantom-deps): First-party @csstools scoped dep declared in package.json; phantom flag is a monorepo artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/css-color-parser | AI (phantom-deps): First-party @csstools scoped dep declared in package.json; phantom flag is a monorepo artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/css-parser-algorithms | AI (phantom-deps): First-party @csstools scoped dep declared in package.json; phantom flag is a monorepo artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@csstools/postcss-progressive-custom-properties | AI (phantom-deps): First-party @csstools scoped dep declared in package.json; phantom flag is a monorepo artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@csstools/utilities | AI (dependencies): @csstools/utilities is a first-party package from the same csstools org/publisher; unvetted flag is a process artifact. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a well-known permissive license; csstools consistently uses it across their plugin suite. Not a real risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 8.0.4 | 5 / 0 | |
| 8.0.3 | 5 / 0 | |
| 8.0.2 | 5 / 0 | |
| 8.0.1 | 5 / 0 | |
| 8.0.0 | 5 / 0 |
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.