On your own
See what a pull brought in. No agent, no AI.
enola baseline pin
git pull
enola checkLinked across repositories.
Even when the paths don’t match.
Give Enola a backend and the apps that call it, and each call is linked to the code that serves it. Change an endpoint and you see who calls it, in every repository.
Four ways to use it
One graph. Use it wherever you work.
In CI
The same check on every pull request, annotated on the lines that caused it.
uses: enola-labs/enola-action@v2With your coding agent
The agent asks what depends on the code before it edits, and checks itself after.
enola install --hooks
claude mcp add enola enolaAs a foundation
A snapshot is plain files in a documented format. Cognee builds its code search on it.
Build on EnolaTests check behavior.
Enola checks structure.
Pin the graph, make the change, compare. Enola reports only what the change introduced, and fails only the rules you chose.
View on GitHubcompiles, tests pass, layer order broken
$enola check --fail-on=layers
FAIL — 1 structural regression introduced.
Regressions (fail):
$echo $?
293findings in benchmark repository
1reported
Existing debt stays silent, so the check can stay on.
Measured, not claimed
Public benchmarks.
Scripts included.
23
Languages and formats in one graph
Discourse’s Ruby and Ember halves, linked.
91 / 91
Reproducible graphs
Public repositories produced byte-identical graphs across a cold run and two warm ones.
20 / 20
Injected cycles caught
None of 1,859 pre-existing findings repeated as new.
Free, local, open source
The whole engine.
No license required.
Use the full open-source engine on your own, or roll out Enola across your organization with Enola Enterprise.