← Home

postcss-color-functional-notation

npm Repository Homepage

Use space and slash separated color notation in CSS

5
Versions
MIT-0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jonathantnealalagunaromainmenke

Keywords

colorcommacssdesignfunctionalhslhslahwbnotationpostcsspostcss-pluginrgbrgbaspacesyntax

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@csstools/utilities AI (phantom-deps): First-party csstools dependency; phantom detection is a false positive for this ESM monorepo plugin package. ai
phantom-deps phantom-dep:@csstools/css-tokenizer AI (phantom-deps): First-party csstools dependency; phantom detection is a false positive for this ESM monorepo plugin package. ai
phantom-deps phantom-dep:@csstools/css-color-parser AI (phantom-deps): First-party csstools dependency; phantom detection is a false positive for this ESM monorepo plugin package. ai
phantom-deps phantom-dep:@csstools/css-parser-algorithms AI (phantom-deps): First-party csstools dependency; phantom detection is a false positive for this ESM monorepo plugin package. ai
phantom-deps phantom-dep:@csstools/postcss-progressive-custom-properties AI (phantom-deps): First-party csstools dependency; phantom detection is a false positive for this ESM monorepo plugin package. ai
license uncommon-license:MIT-0 AI (license): MIT-0 is a recognized permissive open-source license (MIT without attribution requirement); no legal concern for this package. 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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v8.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.