jeremyjh/dialyxir
This system is a static analysis tool for Elixir projects that wraps the Dialyzer type checker. It provides a structured interface for managing PLT files, filtering warnings, and formatting output in various formats including GitHub Actions annotations. The tool supports comprehensive configuration for ignore lists, strict mode, and umbrella projects, while offering detailed, actionable feedback on type mismatches and other static analysis issues.
69.4
Adequate · 1 August 2026
3.7k
lines of production code
Elixir
primary language
2
bus factor · 111 authors in all
3
measurements over time
How it got here
2013 · Configuration and test coverage
This period focused on standardizing the project's development environment by adding default configuration files for Elixir tooling and version management. It also introduced runtime warnings to prevent misconfiguration and expanded test coverage for new OTP 28 warning types and dialyzer options.
4 changes
2014–2016 · Dialyzer task redesign
This period focused on a comprehensive redesign of the `mix dialyzer` task, introducing granular control over PLT management and flexible output formatting. The implementation was supported by modular refactoring of the dialyzer execution and warning processing, alongside the addition of comprehensive unit tests and test fixtures to ensure reliability.
4 changes
2018 · Dialyzer warning improvements
This period focused on enhancing the user experience of static analysis by refactoring warning messages to be more detailed and consistent. The work included expanding the Dialyzer warning modules, creating a standalone task for explaining warnings, and adding comprehensive tests for task behavior and ignore file handling.
4 changes
2019–2024 · Dialyzer test coverage expansion
This period focused on expanding test coverage for Dialyzer warning scenarios by adding numerous test cases and fixture files. The work involved creating specific test examples for various warning types and establishing ignore rules to handle expected warnings in the test suite.
4 changes
Survey your own repository
jeremyjh/dialyxir 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 1 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 3553678f4d — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.