sasa1977/boundary
Boundary is an Elixir library and tooling suite designed to enforce and visualize architectural module boundaries. It provides a declarative API for defining package dependencies and exports, enabling compile-time validation of cross-module calls and detection of circular dependencies. The system also includes Mix tasks for generating dependency graphs and documentation, allowing developers to inspect and visualize the structure of their applications.
66.0
Adequate · 1 August 2026
2.7k
lines of production code
Elixir
primary language
1
bus factor · 19 authors in all
3
measurements over time
How it got here
2019 · Boundary configuration migration
The project underwent a significant architectural shift, renaming from 'Boundaries' to 'Boundary' and migrating from file-based configuration to a declarative, module-based approach using the `use Boundary` macro. This change integrated static analysis and dependency validation directly into the codebase, replacing external configuration files with explicit module definitions. The period also involved updating dependencies and refactoring the test infrastructure to support this new configuration model.
10 changes
2020–2023 · compiler enforcement and visualization tooling
This period focused on implementing the core compiler task to enforce module boundaries and introducing a suite of Mix tasks for dependency analysis and graph visualization. The work included adding extensive test coverage for these new features, ensuring the system correctly identifies and reports cross-boundary violations and generates accurate dependency graphs.
8 changes
Survey your own repository
sasa1977/boundary 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 da77b9bdad — 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.