← Home

postcss-color-function

PostCSS plugin to transform W3C CSS color function to more compatible CSS.

11
Versions
MIT
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

jonathantnealmooxsemigradsky

Keywords

csspostcsspostcss-plugincolorcolourfunction

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jonathantneal is a prolific, trusted PostCSS ecosystem maintainer (675 approved, 0 rejected). Legitimate maintainer transition. ai
publish-pattern dormant-publish AI (publish-pattern): Mature PostCSS plugin with infrequent updates; publish by trusted maintainer jonathantneal is not suspicious. ai

Versions (showing 11 of 11)

Version Deps Published
4.1.0 4 / 4
4.0.1 4 / 3
4.0.0 4 / 3
3.0.0 4 / 4
2.0.1 4 / 4
2.0.0 4 / 3
1.3.2 4 / 3
1.3.0 4 / 3
1.2.0 3 / 4
1.1.0 3 / 4
1.0.0 2 / 4

v4.1.0

2 findings
HIGH Publisher changed: semigradsky → jonathantneal (on 2019-04-01) provenance

This version was published by a different npm account than previous versions on 2019-04-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: moox → semigradsky (on 2017-05-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-05-15. This could indicate a legitimate maintainer transition or an account compromise.

v3.0.0

1 finding
LOW No provenance attestation provenance

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