Skip to content
CAI
Produce a survey ↗Verify a survey

waku-py/waku

Waku is a Python application framework that provides a structured environment for building modular applications with a focus on dependency injection, messaging, and event sourcing. It offers a unified messaging bus supporting CQRS and pipeline behaviors, alongside a complete event sourcing system with aggregate and decider support. The framework emphasizes code quality through automated linting and type checking, and includes a robust extension system for managing application lifecycle and module initialization.

71.0

Strong · 4 August 2026

8.8k

lines of production code

Python

primary language

1

bus factor · 5 authors in all

3

measurements over time

CAI band scale
CAI trend line

How it got here

2024 · Waku framework and DI rewrite

The project underwent a significant architectural shift by introducing the new Waku application framework and a simplified dependency injection system built on Dishka. This period focused on replacing legacy modular components with a structured development workflow, updated tooling, and comprehensive test coverage for the new validation rules.

7 changes

2025 · Dependency injection and module system

This period focused on introducing a robust dependency injection and module system, featuring a new ModuleRegistry, extension lifecycle hooks, and a validation framework for dependency accessibility. Comprehensive test coverage was added to verify the behavior of the DI framework, extension registry, and testing utilities.

9 changes

2026 · Event sourcing and messaging subsystems

This period focused on implementing and testing two major new subsystems: an event sourcing framework with aggregate and decider support, and a unified messaging bus with explicit routing and pipeline behaviors. Comprehensive test suites were added for both domains, covering storage backends, projection runners, snapshotting, and message dispatching.

11 changes

CAI lens gauges

Survey your own repository

waku-py/waku 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 the surveyor at a repository you know and see whether you agree with it.

Survey a repository

About this page

  • The description of this project is derived from its own commit history, not from its README.
  • The score is its highest published measurement, taken on 4 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 658f0b8f63 — the exact code this score is about.
  • Scored under rubric rubric-2026.08.19. Score the same commit under that rubric and you get the same number.
CAI link cards