chroma-js (BSD-3-Clause AND Apache-2.0) 51 versions

chroma-js

npm Repository Homepage

JavaScript library for color conversions

51

Versions

(BSD-3-Clause AND Apache-2.0)

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

celtra-sysadmindejancjsceltra-devexgka

Keywords

color

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): chroma-js is published manually by its long-standing author gka; lack of Sigstore provenance is informational, not a risk signal for this package.	ai	2026/04/23

Versions (showing 51 of 63)

View all versions

Version	Deps	Published
3.2.0	0 / 16	2025-11-28
3.1.4	0 / 16	2025-11-27
3.1.2	0 / 16	2024-10-13
3.1.1	0 / 16	2024-09-08
3.1.0	0 / 16	2024-09-08
3.0.0	0 / 16	2024-08-17
2.6.0	0 / 18	2024-07-30
2.5.0	0 / 18	2024-07-30
2.4.2	0 / 16	2022-02-03
2.4.1	0 / 16	2022-02-03
2.4.0	0 / 16	2022-02-03
2.3.0	0 / 16	2022-01-27
2.2.0	0 / 16	2022-01-27
2.1.2	1 / 15	2021-05-19
2.1.1	1 / 15	2021-03-03
2.1.0	1 / 15	2019-10-31
2.0.6	0 / 15	2019-08-28
2.0.5	0 / 15	2019-08-28
2.0.4	0 / 15	2019-06-17
2.0.3	0 / 15	2019-02-16
2.0.2	0 / 12	2018-12-11
2.0.1	0 / 12	2018-12-11
2.0.0	0 / 12	2018-12-10
1.4.1	0 / 15	2018-11-27
1.4.0	0 / 12	2018-09-24
1.3.7	0 / 12	2018-04-30
1.3.6	0 / 12	2018-01-22
1.3.5	0 / 12	2017-12-16
1.3.4	0 / 12	2017-05-29
1.3.3	0 / 12	2017-04-06
1.3.2	0 / 12	2017-04-04
1.3.1	0 / 12	2017-04-04
1.3.0	0 / 12	2017-04-04
1.2.2	0 / 11	2017-02-08
1.2.1	0 / 11	2016-07-20
1.1.1	0 / 10	2015-07-22
1.1.0	0 / 10	2015-07-19
1.0.1	0 / 10	2015-07-02
0.7.8	0 / 9	2015-06-02
0.7.6	0 / 9	2015-06-01
0.7.5	0 / 9	2015-06-01
0.7.4	0 / 8	2015-05-24
0.7.3	0 / 8	2015-05-24
0.7.2	0 / 4	2015-03-31
0.7.1	0 / 4	2015-03-31
0.6.3	0 / 4	2014-12-26
0.6.2	0 / 4	2014-12-16
0.6.1	0 / 4	2014-10-21
0.6.0	0 / 4	2014-10-17
0.5.9	0 / 3	2014-09-08
0.5.8	0 / 3	2014-09-08

v3.2.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gka.

LOW No provenance attestation provenance

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

v3.1.4

1 finding

INFO No provenance attestation provenance

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

v3.1.2

1 finding

INFO No provenance attestation provenance

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

v3.1.1

1 finding

INFO No provenance attestation provenance

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

v3.1.0

1 finding

INFO No provenance attestation provenance

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

v3.0.0

1 finding

INFO No provenance attestation provenance

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

v2.6.0

1 finding

INFO No provenance attestation provenance

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

v2.5.0

1 finding

INFO No provenance attestation provenance

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

v2.4.2

1 finding

INFO No provenance attestation provenance

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

v2.4.1

1 finding

INFO No provenance attestation provenance

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

v2.4.0

1 finding

INFO No provenance attestation provenance

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

v2.3.0

1 finding

INFO No provenance attestation provenance

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

v2.2.0

1 finding

INFO No provenance attestation provenance

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

v2.1.2

1 finding

INFO No provenance attestation provenance

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

v2.1.1

1 finding

INFO No provenance attestation provenance

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

v2.1.0

1 finding

INFO No provenance attestation provenance

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

v2.0.6

1 finding

INFO No provenance attestation provenance

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

v2.0.5

1 finding

INFO No provenance attestation provenance

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

v2.0.4

1 finding

INFO No provenance attestation provenance

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

v2.0.3

1 finding

INFO No provenance attestation provenance

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

v2.0.2

1 finding

INFO No provenance attestation provenance

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

v2.0.1

1 finding

INFO No provenance attestation provenance

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

v2.0.0

1 finding

INFO No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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