RepoPilot

chroma-core/chroma vs cube-js/cube

Both showing Healthy signals — pick on fit, not health

As of September 2026, chroma and cube both show healthy maintenance signals. chroma was committed to 1 week ago with 9+ active contributors, while cube was committed to 1 week ago with 12+ active contributors. chroma is Apache-2.0-licensed while cube is MIT-licensed. Neither has known critical or high-severity CVEs in its dependency tree.

Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.

chroma-core/chroma

Healthy

Strong maintenance signals

HealthyDependency

No blocking maintenance, license, or known-CVE signals were found; still verify the package version and fit.

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Token-Permissions" is 0/10; 8 cyclic import chains — pervasive coupling

  • Last commit today
  • 9 active contributors
  • Distributed ownership (top contributor 41% of recent commits)
  • Apache-2.0 licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Token-Permissions" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

cube-js/cube

Healthy

Strong maintenance signals

MixedDependency

dependency CVE scan unavailable

HealthyFork & modify

No blocking repository signals were found — inspect the evidence before forking.

HealthyLearn from

Documented and popular — useful reference codebase to read through.

MixedDeploy as-is

Scorecard "Branch-Protection" is 0/10; 7 cyclic import chains — pervasive coupling…

  • Scorecard: default branch unprotected (0/10)
  • Last commit today
  • 12 active contributors
  • Distributed ownership (top contributor 24% of recent commits)
  • MIT licensed
  • CI configured
  • Tests present

What would improve this?

  • Deploy as-is Mixed to Healthy if: bring "Branch-Protection" to ≥3/10 (see scorecard report)

Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

Signal-by-signal breakdown

chromacube
Stars29,21920,776
Last commit12d ago11d ago
LicenseApache-2.0MIT
Open issues8231,159
Has tests
Has CI
Test coverage33%73%
Dependency CVEsNo CVEsNo CVEs
Architecture gradeCC
Cycles87
Bottom-lineHealthy signalsHealthy signals

Want the full analysis? chroma-core/chroma · cube-js/cube

Ask AI about chroma-core/chroma vs cube-js/cube

Open the chat with a comparison question pre-filled.