Skip to content
DevUtils Online

AI Agents

ECC vs Vane

ECC leads by 19.1 · decisive

A · leads

ECC

99.1

305,069 stars · MIT

B

Vane

80.0

38,231 stars · MIT

ECC versus Vane is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ECC is written mainly in JavaScript; Vane is written mainly in TypeScript. The composite score is 99.1 for ECC and 80.0 for Vane.

ECC has 305,069 GitHub stars to Vane's 38,231, a gap of 266,838 (7.98×). Forks are 44,923 for ECC and 4,305 for Vane. On the log scale used inside this pair, adoption is 100 versus 84, and the fork community is 100 versus 78.

Push history: ECC was last pushed on 17 November 2026 (0 days ago), and Vane was last pushed on 01 September 2026 (77 days ago). Open issues stand at 149 for ECC (0.000 per star) and 384 for Vane (0.010 per star). Issue-health scores are 96 and 84; activity scores are 100 and 58.

Both ECC and Vane are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In AI Agents, both ECC (305,069 stars) and Vane (38,231 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: ECC is open source, Vane is open source.

ECC is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 42 points (100 vs 58), and the tightest is self-hosting at 0 points (100 vs 100).

ECC finishes ahead at 99.1 against Vane at 80.0, a 19.1 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

ECC versus Vane metrics
Signal ECC Vane
GitHub stars 305,069 38,231
Forks 44,923 4,305
Open issues 149 384
Adoption 100 84
Activity 100 58
Community 100 78
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 99.1 80.0

ECC

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, ECC or Vane?

ECC has more GitHub stars: 305,069 versus 38,231 for Vane. The gap is 266,838 stars.

Which was updated more recently, ECC or Vane?

ECC was pushed more recently: 17 November 2026 versus 01 September 2026 for Vane. That is 77 days apart.

Can I self-host both ECC and Vane?

Yes. This catalog marks both ECC and Vane as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, ECC or Vane?

ECC is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Vane is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the ECC vs Vane score?

ECC scores 99.1 and Vane scores 80.0. This page calls that a decisive lead for ECC.

Related comparisons