jeremyjh/dialyxir
Dialyxir is an Elixir wrapper for the Dialyzer static analysis tool, designed to integrate type checking into the Elixir build process. It provides a unified Mix task to manage PLT files, compile projects, and format diagnostic warnings in various styles including GitHub Actions annotations. The system supports filtering and ignoring specific warnings, with comprehensive test coverage ensuring compatibility with modern OTP versions.
69.8
Adequate · 6 August 2026
3.7k
lines of production code
Elixir
primary language
2
bus factor · 111 authors in all
4
measurements over time
How it got here
2013 · Initial project scaffolding and configuration
The period focused on establishing the foundational structure of the project, including essential configuration files and development environment specifications. It also introduced behavioral changes to improve build efficiency and expanded test coverage to support new Erlang/OTP 28 warning types and configuration options.
4 changes
2014–2016 · Dialyzer task and modular architecture
This period focused on introducing the `mix dialyzer` task, providing a unified interface for running Dialyzer with configurable output formats and PLT management. The underlying implementation was refactored into a modular architecture with distinct formatters and filters, accompanied by comprehensive test coverage and umbrella project fixtures.
4 changes
2018 · Dialyzer diagnostics and test coverage
This period focused on enhancing the Elixir static analysis tooling by expanding Dialyzer warning messages to provide more specific and detailed diagnostics. The work also included adding comprehensive tests for the Mix Dialyzer task and the ignore file parser, while refactoring the codebase to improve maintainability.
4 changes
2019–2024 · Dialyzer test coverage
This period focused on expanding test coverage for the Dialyzer integration by adding specific test fixtures and examples. The work included creating test cases for various warning scenarios, such as function application arguments, callback mismatches, and opaque type equality, as well as handling edge cases in ignore file processing.
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 6 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.19. Score the same commit under that rubric and you get the same number.