← Home

postcss-color-mod-function

Modify colors using the color-mod() function in CSS

16
Versions
CC0-1.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

romainmenkealagunajonathantneal

Keywords

postcsscsspostcss-plugincolorscoloursmodificationsmodsadjustersadjustmentscsswgrgbahslawhiteblackredgreenbluealphahuesaturationlightnesswhitenessblacknesstintshadeblendacontrast

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): romainmenke is a highly trusted publisher (897 approved/0 rejected) and a known PostCSS ecosystem maintainer; this reflects a legitimate jonathantneal → csstools/romainmenke handoff pattern. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers romainmenke and alaguna are consistent with the established csstools org taking over PostCSS plugin maintenance from jonathantneal. ai

Versions (showing 16 of 16)

Version Deps Published
4.1.1 2 / 3
4.1.0 2 / 3
4.0.0 2 / 4
3.0.3 3 / 10
3.0.2 3 / 10
3.0.1 3 / 11
3.0.0 3 / 11
2.4.3 3 / 10
2.4.2 3 / 10
2.4.1 3 / 10
2.4.0 3 / 10
2.3.0 3 / 10
2.2.0 3 / 10
2.1.0 2 / 10
1.1.0 3 / 10
1.0.0 3 / 10

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

2 findings
HIGH Publisher changed: jonathantneal → romainmenke (on 2024-10-18) provenance

This version was published by a different npm account than previous versions on 2024-10-18. 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.0

2 findings
HIGH Publisher changed: jonathantneal → romainmenke (on 2024-10-18) provenance

This version was published by a different npm account than previous versions on 2024-10-18. 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.

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

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.