Skip to content
CAI
Software that uses CAICheck a score

AdRoll/mero

65.3

Adequate · 2 October 2026

3.2k

lines of production code

Erlang

primary language

2

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Mero is a Memcached client library that supports multiple clusters with automatic AWS ElastiCache discovery and per-cluster configuration. It implements a binary protocol with support for pipelined operations and Compare-And-Swap (CAS) mechanics. The system is built using rebar3 and includes comprehensive test coverage for cluster lifecycle and protocol handling.

Features

Support for per-cluster configuration and Elasticache auto-discovery

Mero now supports configuring multiple memcached clusters with independent settings (such as timeouts and connection limits) rather than a single global configuration. It includes automatic discovery of AWS ElastiCache cluster topologies via the config endpoint, allowing the client to dynamically detect and manage cluster membership changes. The configuration system also introduces a heartbeat mechanism to monitor and reload cluster definitions without requiring a restart.

src · high confidence

Behavioural changes

Add binary protocol commands and error codes to header

The include/mero.hrl header now defines new binary protocol command codes for pipelined operations (MEMCACHE\_INCREMENTQ, SETQ, ADDQ, DELETEQ) and a comprehensive set of error codes (e.g., VALUE\_TOO\_LARGE, NON\_NUMERIC\_INCR, OOM). It also introduces a mero\_item record with a cas field to support Compare-And-Swap (CAS) operations and updates the logging macro structure.

include · high confidence

Migration to rebar3 and enhanced build tooling

The project has migrated its build system from a custom Makefile to rebar3, introducing a standardized workflow for compilation, testing, and linting. This change brings several developer-facing improvements: dependency management is now handled via a rebar.lock file with pinned versions (e.g., dynamic\_compile 1.0.0); code quality is enforced through integrated dialyzer, xref, and elvis linting rules; and the build process now supports OTP 25+ (as indicated by minimum\_otp\_vsn) and includes coverage reporting. Additionally, new configuration files (.gitignore, CONTRIBUTING.md, elvis.config) and a CHANGELOG entry clarify contribution guidelines and project structure.

(repo-wide) · high confidence

Removal of ebin/.placeholder file

The placeholder file in the ebin directory has been removed, likely as part of the migration from Makefile to rebar3 which handles the compilation output directory differently.

ebin · medium confidence

Test coverage

Expanded test coverage for cluster configuration, protocol workers, and cluster lifecycle

Added new Common Test suites to verify cluster configuration processing (\mero\_conf\_monitor\_SUITE\, \mero\_conf\_SUITE\), binary and text protocol worker response parsing (\mero\_wrk\_tcp\_binary\_SUITE\, \mero\_wrk\_tcp\_txt\_SUITE\), and cluster availability/restart logic (\mero\_cluster\_SUITE\). The existing \mero\_SUITE\ was refactored to group tests by protocol and include multi-key operations (\madd\, \mset\, \mcas\), while \mero\_test\_localhost\_SUITE\ was removed in favor of the new structured suites.

test · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 69 → 65 (-3.7)
  • Rubric changed (rubric-2026.09.12 → rubric-2026.09.18) — scores are not directly comparable.

Lenses

  • Code Health 94 → 94 (+0.0)
  • Architecture 100 → 100 (+0.0)
  • Maturity 49 → 49 (+0.0)
  • Readiness 78 → 63 (-14.7)
  • Security 97 → 99 (+1.5)

Resolved (4)

  • Coverage not measured — no coverage collector is wired up
  • Documentation: no installation or build instructions (README.md)
  • Documentation: no usage examples (README.md)
  • Off-boarding risk: anonymized user #1

New (1)

  • Off-boarding risk: anonymized user #1

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

AdRoll/mero was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 2 October 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit f734d2c40af3b4cd4b46e61cb1ba258ce8e71620 — the exact code this score is about.
  • Scored under rubric-2026.09.18 — the same rubric and the same method as every other entry in this index.
  • Measured by watchdog.canine.dev using codehealth-analyzer preprod-e569280dd5e2.