onecolor
Javascript color object with implicit color space conversions. Supports RGB, HSV, HSL and CMYK with alpha channel.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Browserify bundle uses numeric module IDs (require(7), require(6), etc.) — standard bundler output, not arbitrary dynamic requires. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2016, before Sigstore provenance existed. Expected for this era of packages. | ai | |
| provenance | publisher-changed | AI (provenance): Both munter and papandreou are listed maintainers; papandreou has published all 36 approved versions since 2018. Legitimate maintainer transition. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 0 / 19 | |
| 4.0.0 | 0 / 19 | |
| 3.1.0 | 0 / 9 | |
| 3.0.5 | 0 / 9 | |
| 3.0.4 | 0 / 9 | |
| 3.0.3 | 0 / 9 | |
| 3.0.2 | 0 / 9 | |
| 3.0.1 | 0 / 9 | |
| 3.0.0 | 0 / 9 | |
| 2.5.0 | 0 / 6 | |
| 2.4.2 | 0 / 5 | |
| 2.4.1 | 0 / 4 | |
| 2.4.0 | 0 / 4 | |
| 2.3.4 | 0 / 4 | |
| 2.3.3 | 0 / 5 | |
| 2.3.2 | 0 / 5 | |
| 2.3.1 | 0 / 5 | |
| 2.3.0 | 0 / 4 | |
| 2.2.9 | 0 / 4 | |
| 2.2.8 | 0 / 4 | |
| 2.2.7 | 0 / 4 | |
| 2.2.6 | 0 / 4 | |
| 2.2.5 | 0 / 4 | |
| 2.2.4 | 0 / 4 | |
| 2.2.3 | 0 / 4 | |
| 2.2.2 | 0 / 4 | |
| 2.2.1 | 0 / 4 | |
| 2.2.0 | 0 / 3 | |
| 2.1.0 | 0 / 3 | |
| 2.0.7 | 0 / 3 | |
| 2.0.6 | 0 / 3 | |
| 2.0.5 | 0 / 3 | |
| 2.0.4 | 0 / 1 | |
| 2.0.3 | 0 / 1 | |
| 2.0.2 | 0 / 1 | |
| 2.0.1 | 0 / 1 |
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-09-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-21. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsThis version was published by a different npm account than previous versions on 2016-05-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-04-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-15. This could indicate a legitimate maintainer transition or an account compromise.