color-space Unlicense 51 versions

color-space

npm Repository Homepage

Collection of color space conversions

51

Versions

Unlicense

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

mikolalysenkojaspervdgdfcreativehughskrreusserdy

Keywords

colorcolourcolor-spacegamutcolor-convertcolor-conversioncolor-conversionscolor-translationcolor-mathcolor-datargbxyzhslhsvhsihwbcmykcmyxyyyiqyuvydbdrycgcoypbprycbcrxvyccyccbccrcucsuvwjpeglablabhlmslchabluvlchuvhsluvhpluvcubehelixcoloroidhcghcytslyesosaucshsphsmlrgboklab

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): dfcreative and dy appear to be the same person (Dmitry Ivanov); dy has a long, clean npm track record (91 approved, 0 rejected, 2464 days). Legitimate account transition.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer 'dy' is the same author under a different npm handle, with a clean 2464-day track record. No compromise indicators.	ai	2026/04/24

Versions (showing 51 of 55)

View all versions

Version	Deps	Published
2.3.2	0 / 3	2025-05-11
2.3.1	0 / 3	2025-02-02
2.3.0	0 / 2	2025-02-01
2.2.0	0 / 3	2025-02-01
2.1.1	0 / 3	2025-01-29
2.1.0	0 / 6	2025-01-22
2.0.1	0 / 4	2023-06-25
2.0.0	0 / 4	2022-01-25
1.16.0	2 / 5	2018-03-05
1.15.0	2 / 5	2017-10-06
1.14.7	2 / 5	2016-11-22
1.14.6	2 / 5	2016-08-21
1.14.5	2 / 5	2016-08-14
1.14.4	2 / 5	2016-08-14
1.14.3	3 / 5	2016-02-05
1.14.2	3 / 5	2016-02-01
1.14.1	3 / 5	2016-02-01
1.14.0	3 / 5	2016-02-01
1.13.0	2 / 5	2015-09-23
1.12.0	3 / 3	2015-09-19
1.11.2	3 / 3	2015-09-10
1.11.0	3 / 3	2015-09-09
1.10.0	3 / 3	2015-09-08
1.9.0	3 / 3	2015-09-07
1.8.0	3 / 3	2015-09-06
1.7.0	3 / 3	2015-09-05
1.6.0	3 / 3	2015-09-04
1.5.0	3 / 3	2015-09-02
1.4.1	3 / 3	2015-06-20
1.3.1	2 / 6	2015-06-18
1.3.0	2 / 6	2015-06-18
1.2.1	1 / 7	2015-06-15
1.2.0	1 / 7	2015-06-15
1.1.3	1 / 7	2015-06-14
1.1.2	1 / 7	2014-12-14
1.1.1	1 / 7	2014-12-03
1.1.0	1 / 7	2014-12-01
1.0.4	1 / 7	2014-11-29
1.0.3	1 / 7	2014-11-29
1.0.2	1 / 7	2014-11-29
1.0.1	1 / 7	2014-11-29
1.0.0	1 / 7	2014-11-29
0.5.1	1 / 7	2014-11-29
0.5.0	1 / 7	2014-11-29
0.4.0	1 / 7	2014-11-28
0.3.3	0 / 7	2014-11-28
0.3.2	0 / 7	2014-11-25
0.3.1	0 / 7	2014-11-25
0.3.0	0 / 7	2014-11-25
0.2.1	0 / 7	2014-11-25
0.1.1	0 / 7	2014-11-25

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

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

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

2 findings

HIGH Publisher changed: dfcreative → dy (on 2022-01-25) provenance

This version was published by a different npm account than previous versions on 2022-01-25. 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.

v1.16.0

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.7

1 finding

LOW No provenance attestation provenance

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

v1.14.6

1 finding

LOW No provenance attestation provenance

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

v1.14.5

1 finding

LOW No provenance attestation provenance

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

v1.14.4

1 finding

LOW No provenance attestation provenance

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

v1.14.3

1 finding

LOW No provenance attestation provenance

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

v1.14.2

1 finding

LOW No provenance attestation provenance

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

v1.14.1

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.2

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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