zdenal/commanded_events_map

This system is a visualization tool for Commanded applications, designed to generate and display interactive process maps of commands, events, and handlers. It combines an Elixir backend that scans and analyzes application code with a React-based frontend that renders an interactive graph of the event flow. Users can filter and explore the structure of their Commanded aggregates and handlers through a configurable, regex-driven analysis pipeline.

Introduced a new React application structure under frontend\_client/events-flow-react, including configuration files (.gitignore, README.md, public/index.html, public/manifest.json) and a Koa-based server (server.js) that serves JSON data on port 5000. Additionally, added an Elixir Mix task (lib/mix/tasks/scan\_and\_generate.ex) that executes the Commanded process map, enabling command-line generation of data structures for the events/commands flow.

_frontend\client, lib/mix · high confidence

New executable scripts have been added to the bin directory to streamline local development workflows. The 'generate\_data' script triggers the backend data generation process, while 'run\_client' launches both the server and client applications with hot-reload capabilities tied to data.json changes. The 'setup' script automates the initial project configuration by fetching dependencies and compiling the backend, then installing frontend dependencies.

bin · high confidence

The repository is initialized with a new Elixir-based tool designed to visualize and analyze Commanded applications. The release includes a .tool-versions file specifying Erlang 23.3, Elixir 1.10.3, and Node.js 10.16.3, alongside a MIT license and a .gitignore configuration. The project structure supports a frontend client and backend analysis logic, with a README detailing installation steps to generate and view process maps.

(repo-wide) · high confidence

Added a new React-based frontend for visualizing and filtering event flows. Users can now view an interactive graph of nodes and edges, select specific nodes or edges to filter the view, and adjust the dependency depth. The interface includes a filter panel for selecting nodes and edges, a flow graph visualization using the Vis.js library, and a dialog to view detailed node content.

_frontend\client/events-flow-react · high confidence

The application now supports configurable process mapping for Commanded, allowing users to define how commands, events, and handlers are discovered and processed via regular expressions and output targets. A new \config/dev.tmp.exs\ file introduces these mappings for development, while \config/config.exs\ is updated to import environment-specific configuration files, enabling distinct settings per environment.

config · medium confidence

The logic for identifying and processing Commanded aggregates and handlers has been refactored to rely on configurable regular expressions and exclusion lists rather than hardcoded patterns. The module now reads regex patterns and file paths from the application environment via \config/1\, allowing the definition of 'types' (such as 'aggregate' or 'handler') to be driven by configuration. This replaces the previous approach where file filtering and content analysis were tightly coupled to specific, hard-coded regular expressions and directory structures.

lib · medium confidence

Introduced two new projects: a React-based frontend application (events-flow-react) and a Koa-based server (commanded\_process\_map). The frontend project includes dependencies for Material-UI, React, and Vis.js, while the server project depends on Koa and Koa2-Cors. Additionally, the Elixir project (mix.exs) was updated to include the Poison library for JSON parsing.

(dependencies) · high confidence

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

• CAI 45 → 44 (-1.4)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 67 → 71 (+3.8)
• Architecture 69 → 69 (+0.0)
• Maturity 51 → 36 (-14.4)
• Readiness 29 → 33 (+4.1)
• Security 75 → 75 (+0.0)

• Coverage not included — suite not readable by the collector
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/server/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical vulnerability: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Dependency hygiene not measured — no supported dependency manifest was read
• High CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• …and 36 more

• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/server/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• Critical vulnerability: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• High CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• High CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• High CVE: [GHSA redacted] (frontend_client/events-flow-react/yarn.lock)
• …and 78 more

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

zdenal/commanded_events_map 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.