rrrene/credo
Credo is a static code analysis tool for the Elixir programming language that enforces coding standards and identifies potential issues. It provides a comprehensive suite of checks covering consistency, design, readability, refactoring, and warnings, alongside new capabilities for incremental analysis and code diffing. The system features a modular execution pipeline, multiple output formats, and CLI commands for generating checks and configuration, all supported by an extensive test suite.
60.3
Adequate · 5 August 2026
25k
lines of production code
Elixir
primary language
1
bus factor · 273 authors in all
3
measurements over time
How it got here
2015 · Execution model refactoring and check expansion
This period focused on a major internal refactoring of Credo's execution model, replacing the legacy runner with a new pipeline-based architecture. Concurrently, the project significantly expanded its static analysis capabilities by introducing numerous new checks for consistency, design, readability, and warnings, supported by comprehensive test coverage and CLI improvements.
27 changes
2016–2017 · CLI and execution refactoring
This period focused on refactoring the Credo execution pipeline into a modular task-based architecture, improving concurrency and maintainability. Concurrently, the project introduced several new CLI commands (suggest, list, explain, categories) and expanded output formatting capabilities to support structured data exchange and IDE integration.
23 changes
2018–2026 · CLI command expansion and test infrastructure
This period focused on expanding the Credo CLI with new commands for displaying system information and analyzing code diffs, alongside introducing a robust test helper framework. The work also included adding comprehensive integration and unit tests to validate the new features and ensure regression safety.
15 changes
Survey your own repository
rrrene/credo 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.
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 5 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 89457a1608 — 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.