exponentially/extreme

This system is an Elixir-based client library for interacting with EventStore, supporting both standalone and clustered deployments. It provides mechanisms for reading and writing events, including backward stream reads and transactional writes. The library features robust event processing capabilities, offering standard, fanout, and backpressure-aware listeners to handle high-throughput scenarios. Additionally, it supports persistent subscriptions with acknowledgment-based processing and message parking for failed events.

The library now supports connecting to an EventStore cluster by selecting the appropriate node via a gossip protocol, enabling read/write operations against a distributed EventStore deployment. Additionally, the library introduces persistent subscriptions, allowing asynchronous, server-side tracked subscriptions with acknowledgment-based processing, backpressure management, and message parking for failed events. This includes new modules for cluster connection logic, event production with buffering, and persistent subscription management.

lib/extreme · high confidence

Introduces new listener modules for consuming events from EventStore. The \Extreme.Listener\ module provides a standard GenServer-based listener that reads from a stream and processes events. The \Extreme.FanoutListener\ offers a lightweight alternative that only processes new live events, similar to a fanout exchange. Additionally, \Extreme.ListenerWithBackPressure\ implements a producer-based approach that applies backpressure when the buffer of unprocessed events reaches a configurable threshold, preventing memory issues during high-throughput scenarios.

lib · high confidence

The project now includes a \.formatter.exs\ file to configure \mix format\ for consistent code styling, and a \docker-compose.yml\ to spin up a local Event Store instance for development and testing. Additionally, the \README.md\ has been updated with build status, version, and coverage badges, and the \.gitignore\ has been expanded to exclude common build artifacts and IDE files.

(repo-wide) · high confidence

The project now includes a new \event\_store.proto\ file that defines the Protocol Buffers schema for EventStore version 3.0.5. This adds support for reading events backward, handling transactional writes, and managing stream operations, while removing older PersistentSubscription-related messages.

include · medium confidence

The application now uses separate configuration files for each environment (dev, test, prod) via a shared config/config.exs that imports the current Mix environment. In the test environment, the Extreme client is configured with default connection details (host, port, credentials) and extended assert\_receive\_timeout to 10 seconds. The dev environment enables debug-level console logging, while the prod environment is kept minimal.

config · high confidence

Added comprehensive test suite for EventStore client and listeners; Added test coverage for Extreme client modules; Added test support infrastructure for event handling and leak detection.

The \mix.exs\ and \mix.lock\ files have been updated to refresh the project's dependencies. Key changes include updating \exprotobuf\ to version 1.2.17, \elixir\_uuid\ to 1.2.1, and \telemetry\ to 1.3.0. The Elixir version requirement has been set to \\~\> 1.11\. Additionally, \jason\ is now an optional dependency, and the package configuration has been updated to include the \include\ folder.

(dependencies) · high confidence

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

• CAI 60 → 60 (-0.6)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (-0.5)
• Architecture 100 → 98 (-2.1)
• Maturity 41 → 41 (+0.1)
• Readiness 55 → 55 (+0.0)
• Security 99 → 97 (-2.8)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — no supported dependency manifest was read
• Medium CVE: EEF-[CVE redacted] (mix.lock)
• No exposed public API
• Off-boarding risk: anonymized user #1
• Test reliability not included
• The README is a single badge-driven status page with no description of what Extreme does or how to install/use it. (README.md)

• Documentation: no installation or build instructions (README.md)
• Documentation: no project overview (README.md)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium CVE: EEF-[CVE redacted] (mix.lock)
• Medium IaC: WD-COMPOSE-0002 (docker-compose.yml)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• No dependency advisory monitoring
• …and 4 more

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

exponentially/extreme 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.