Skip to content
DevUtils Online

AI Agents

CloakBrowser vs ECC

ECC leads by 10.8 · clear

B · leads

ECC

99.1

305,069 stars · MIT

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

ECC has 305,069 GitHub stars to CloakBrowser's 32,949, a gap of 272,120 (9.26×). Forks are 2,733 for CloakBrowser and 44,923 for ECC. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 74 versus 100.

Push history: CloakBrowser was last pushed on 17 November 2026 (0 days ago), and ECC was last pushed on 17 November 2026 (0 days ago). Open issues stand at 169 for CloakBrowser (0.005 per star) and 149 for ECC (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

Both CloakBrowser and ECC 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 CloakBrowser (32,949 stars) and ECC (305,069 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: CloakBrowser is open source, ECC is open source.

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

ECC finishes ahead at 99.1 against CloakBrowser at 88.3, a 10.8 point clear 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.

CloakBrowser versus ECC metrics
Signal CloakBrowser ECC
GitHub stars 32,949 305,069
Forks 2,733 44,923
Open issues 169 149
Adoption 82 100
Activity 100 100
Community 74 100
Issue health 84 96
License 96 96
Self-hosting 100 100
Composite 88.3 99.1

CloakBrowser

Stealth Chromium that passes every bot detection test. Drop-in Playwright replacement with source-level fingerprint patches. 50+ tests passed.

Project site · GitHub · Full profile

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, CloakBrowser or ECC?

ECC has more GitHub stars: 305,069 versus 32,949 for CloakBrowser. The gap is 272,120 stars.

Which was updated more recently, CloakBrowser or ECC?

Both were last pushed on 17 November 2026.

Can I self-host both CloakBrowser and ECC?

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

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

CloakBrowser 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the CloakBrowser vs ECC score?

ECC scores 99.1 and CloakBrowser scores 88.3. This page calls that a clear lead for ECC.

Related comparisons