Oeditus Credo
58 custom static analysis checks for Credo in Elixir codebase quality.
extends Credo with 58 production-tested static analysis rules for Elixir projects.
The Pitch
Standard linting tools catch basic syntax and style inconsistencies, but often miss subtle architectural anti-patterns, performance bottlenecks, and domain-specific code risks.
Oeditus Credo provides a comprehensive collection of 58 specialized Credo checks. Designed for strict software quality engineering, it enforces architectural constraints, flags unsafe map operations, uncovers unused abstractions, and ensures uniform coding standards across large Elixir codebases.
Why Oeditus Credo?
58 Battle-Tested Checks
Expands standard Credo checks covering refactoring opportunities, consistency, and hidden bug patterns.
Zero Configuration Setup
Drop into your
.credo.exs
configuration and instantly run enhanced static analysis.
Categorized Guidance
Clear check categories covering Readability, Design, Refactoring, and Code Consistency.
CI/CD Integration
Integrates seamlessly into existing Credo pipeline steps in GitHub Actions and GitLab CI.
The Tech
| Language | Elixir |
| Base Framework | Credo Static Analysis Engine |
| Total Rules | 58 Custom Checks |
| Hex Package |
oeditus_credo
|
Who It's For
- Elixir Architecture Leads enforcing strict team coding guidelines across repos.
- Engineering Teams upgrading legacy codebases and eliminating common anti-patterns.
- Open-Source Maintainers ensuring clean, uniform contribution quality.
Bottom Line
Supercharge your Credo linter with 58 custom production-ready static analysis checks.