chroma-js 2.1.2
JavaScript library for color conversions
chroma-js@2.1.2 was published on 2021-05-19. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All chroma-js versions · Permanent reference to 2.1.2 · Latest release
Package specifications
| Version | 2.1.2 |
|---|---|
| License declaration | (BSD-3-Clause AND Apache-2.0) |
| Published | 2021-05-19T11:03:51.229Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 273.08 KiB |
| Published file count | 98 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | chroma.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 10605 |
| Repository forks | 553 |
Install chroma-js 2.1.2
npm install chroma-js@2.1.2 pnpm add chroma-js@2.1.2 yarn add chroma-js@2.1.2
Runtime dependencies
- cross-env ^6.0.3
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- cross-env@6.0.3 — direct
- cross-spawn@7.0.6 — indirect
- isexe@2.0.0 — indirect
- path-key@3.1.1 — indirect
- shebang-command@2.0.0 — indirect
- shebang-regex@3.0.0 — indirect
- which@2.0.2 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Code-Review | 1/10 — Found 4/29 approved changesets -- score normalized to 1 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Security-Policy | 0/10 — security policy file not detected |
| License | 9/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Branch-Protection | 5/10 — branch protection is not maximal on development and all release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/chroma-js/2.1.2 — retrieved 2026-10-29T16:49:34.800Z
- https://api.deps.dev/v3/projects/github.com%2Fgka%2Fchroma.js — retrieved 2026-10-29T12:01:32.379Z
- https://api.deps.dev/v3/systems/npm/packages/chroma-js/versions/2.1.2:dependencies — retrieved 2026-10-29T16:49:35.351Z
- https://api.deps.dev/v3/systems/npm/packages/chroma-js/versions/2.1.2 — retrieved 2026-10-29T16:49:35.322Z