@csstools/postcss-contrast-color-function MIT-0 25 versions

@csstools/postcss-contrast-color-function

npm Repository Homepage

Dynamically specify a text color with adequate contrast

25

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

contrastcontrast-colorcsspostcss-pluginwcag

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
license	uncommon-license:MIT-0	AI (license): MIT-0 is a well-known permissive license used consistently across the @csstools package suite. Not a risk.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/utilities	AI (phantom-deps): Same-org monorepo dependency; phantom detection is a false positive for this package structure.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-tokenizer	AI (phantom-deps): Same-org monorepo dependency; phantom detection is a false positive for this package structure.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-color-parser	AI (phantom-deps): Same-org monorepo dependency; phantom detection is a false positive for this package structure.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-parser-algorithms	AI (phantom-deps): Same-org monorepo dependency; phantom detection is a false positive for this package structure.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/postcss-progressive-custom-properties	AI (phantom-deps): Same-org monorepo dependency; phantom detection is a false positive for this package structure.	ai	2026/04/21

Versions (showing 25 of 25)

Version	Deps	Published
3.0.4	5 / 0	2026-05-13
3.0.3	5 / 0	2026-04-12
3.0.2	5 / 0	2026-02-21
3.0.1	5 / 0	2026-01-25
3.0.0	5 / 0	2026-01-14
2.0.12	5 / 0	2025-09-21
2.0.11	5 / 0	2025-08-22
2.0.10	5 / 0	2025-05-27
2.0.9	5 / 0	2025-04-19
2.0.8	6 / 0	2025-02-23
2.0.7	6 / 0	2024-12-27
2.0.6	6 / 0	2024-11-11
2.0.5	6 / 0	2024-11-01
2.0.4	6 / 0	2024-10-23
2.0.3	6 / 0	2024-10-10
2.0.2	6 / 0	2024-08-18
2.0.1	6 / 0	2024-08-14
2.0.0	6 / 0	2024-08-03
1.0.6	6 / 0	2024-07-07
1.0.5	6 / 0	2024-07-06
1.0.4	6 / 0	2024-06-29
1.0.3	6 / 0	2024-05-04
1.0.2	6 / 0	2024-05-04
1.0.1	6 / 0	2024-04-21
1.0.0	6 / 0	2024-03-31

v3.0.4

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

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.

v2.0.10

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.

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.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.

v2.0.1

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.

v2.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.

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

1 finding

LOW No provenance attestation provenance

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

v1.0.3

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.

v1.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.

v1.0.1

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.

v1.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.