← Home

@csstools/color-helpers

npm Repository Homepage

Color helpers to ease transformation between formats, gamut, etc

17
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

colorscss

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition within csstools org; romainmenke is a listed contributor and highly trusted publisher (913 approved packages). ai
maintainer-change maintainer-added AI (maintainer-change): romainmenke is a known csstools maintainer with extensive track record; legitimate team membership. ai
license uncommon-license:MIT-0 AI (license): MIT-0 is a recognized permissive license (MIT without attribution requirement); stable for this package. ai

Versions (showing 17 of 17)

Version Deps Published
6.0.2 0 / 0
6.0.1 0 / 0
6.0.0 0 / 0
5.1.0 0 / 0
5.0.2 0 / 0
5.0.1 0 / 0
5.0.0 0 / 0
4.2.1 0 / 0
4.2.0 0 / 0
4.1.0 0 / 0
4.0.0 0 / 0
3.0.2 0 / 0
3.0.1 0 / 0
3.0.0 0 / 0
2.1.0 0 / 0
2.0.0 0 / 0
1.0.0 0 / 0

v6.0.1

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.2.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.

v4.2.0

2 findings
HIGH Publisher changed: alaguna → romainmenke (on 2024-04-21) provenance

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

2 findings
HIGH Publisher changed: alaguna → romainmenke (on 2024-03-31) provenance

This version was published by a different npm account than previous versions on 2024-03-31. 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: alaguna → romainmenke (on 2023-12-15) provenance

This version was published by a different npm account than previous versions on 2023-12-15. 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.2

2 findings
HIGH Publisher changed: alaguna → romainmenke (on 2023-09-02) provenance

This version was published by a different npm account than previous versions on 2023-09-02. 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.1

2 findings
HIGH Publisher changed: alaguna → romainmenke (on 2023-08-28) provenance

This version was published by a different npm account than previous versions on 2023-08-28. 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.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.1.0

1 finding
LOW No provenance attestation provenance

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

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