enola
Architectural regression testing for AI-assisted development.
Catch structural regressions that builds and tests cannot see: new dependency cycles, violated layer boundaries, undeclared service dependencies, and changes that spread beyond their intended scope.
Enola maps your codebase before a change and compares it with the structure afterward. The result is about this change, not every problem already in the repository, and only the rules you choose can fail the build.
- Exact, local measurement. Parsed source and graph algorithms. No model, no embeddings, no upload, no account, no license check.
- One graph across the repository. 23 languages and formats, detected automatically and combined into one baseline and verdict.
- One loop everywhere. Your coding agent reads the graph before it edits and receives the verdict afterward. The same check runs from the CLI or in CI.
Install
pip install enola-cli
The command is enola. This package ships a prebuilt binary, so there is no
Python dependency at run time and nothing is importable from Python.
Got this package with Cognee? You already have all of enola. See https://github.com/enola-labs/enola/blob/main/docs/COGNEE.md.
Try it read-only
enola --explain /path/to/your/repo
No baseline, config file or MCP client, and nothing is written to disk. Enola prints the architecture it measured (patterns, cycles, layer violations, hotspots, blast radius and structural outliers) and exits.
Documentation
Full documentation, including the CLI reference and architecture internals, lives at https://github.com/enola-labs/enola.
1 maintainer
Metadata
1 maintainer
Release files for enola-cli 0.4.33
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| enola_cli-0.4.33-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| enola_cli-0.4.33-py3-none-musllinux_1_2_x86_64.whl | Python 3 | none | Linux musl 1.2+ x86-64 | Details |
| enola_cli-0.4.33-py3-none-musllinux_1_2_aarch64.whl | Python 3 | none | Linux musl 1.2+ ARM64 | Details |
| enola_cli-0.4.33-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| enola_cli-0.4.33-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| enola_cli-0.4.33-py3-none-macosx_12_0_x86_64.whl | Python 3 | none | macOS 12.0+ x86-64 | Details |
| enola_cli-0.4.33-py3-none-macosx_12_0_arm64.whl | Python 3 | none | macOS 12.0+ ARM64 | Details |
Total release size: 86.5 MB
Release files / enola_cli-0.4.33-py3-none-win_amd64.whl
| Download URL | enola_cli-0.4.33-py3-none-win_amd64.whl |
|---|---|
| Size | 12.9 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8ac41caa8b54be454af1c17d2bca53ae1ac293fe09f059f6e7e4f6e0e709ca5b
|
|
BLAKE2b-256 checksum How to use checksums |
ab2360aa71cb0222cb9974ca7d712fdacfb8b60de673dbc8cac118dd84ca57d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / enola_cli-0.4.33-py3-none-musllinux_1_2_x86_64.whl
| Download URL | enola_cli-0.4.33-py3-none-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 12.7 MB |
| Tags | Linux musl 1.2+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
ae3926e1ffa64aa38a3c03d03e08a36475e2c316bc059798ae922a741fc297c1
|
|
BLAKE2b-256 checksum How to use checksums |
402c0b86d28b6c3edf9a5852fc79ad9c59347af35d667f3e5853b1c9b33293f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / enola_cli-0.4.33-py3-none-musllinux_1_2_aarch64.whl
| Download URL | enola_cli-0.4.33-py3-none-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 11.6 MB |
| Tags | Linux musl 1.2+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
65351b87c51a1ca94fd3e3ec3e5dbe3391c7968fc3454c4da385b7425e35b0ad
|
|
BLAKE2b-256 checksum How to use checksums |
5917f2f32903dfbaec9ede660e8d8e89db1a25f20cc37c50a526ec21f6054f09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / enola_cli-0.4.33-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | enola_cli-0.4.33-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 12.7 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
c1d31e9e5a91fa88c09b08854b001ad932bb0ad1394c604126c09a9ab514ac8a
|
|
BLAKE2b-256 checksum How to use checksums |
f00b9414591b4c36a955c102d809c4cd0c08947362771a9e240c471986e3fec1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / enola_cli-0.4.33-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | enola_cli-0.4.33-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 11.6 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
6edf58470f811b2d573843981da3752b81eddeda49a29855303eef97d2824240
|
|
BLAKE2b-256 checksum How to use checksums |
d9fabd49aad6af25ea8c69534da7a3bb60edbc3c827e1ffc280c5d5972edb36d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / enola_cli-0.4.33-py3-none-macosx_12_0_x86_64.whl
| Download URL | enola_cli-0.4.33-py3-none-macosx_12_0_x86_64.whl |
|---|---|
| Size | 12.8 MB |
| Tags | Python 3 macOS 12.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
9640a351e9249f34137bc14e589ab9dd170140d7cbc9827b98622c058a1ad75b
|
|
BLAKE2b-256 checksum How to use checksums |
9afc88f44ad2a5d52d8e971be55aefc9ff230771d46a2aa051e5f30ee65ba78b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / enola_cli-0.4.33-py3-none-macosx_12_0_arm64.whl
| Download URL | enola_cli-0.4.33-py3-none-macosx_12_0_arm64.whl |
|---|---|
| Size | 12.1 MB |
| Tags | Python 3 macOS 12.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
89c33979840c8777e070da62d3c958b620541d776a6c90574c47a0feaa5d3f4b
|
|
BLAKE2b-256 checksum How to use checksums |
7dae2f92f9c8bab6f5a7be8aa20c68f90fa27b3a8be3e1eceb0e9fd68bebd7ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for enola-cli 0.4.33
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 7 files in this release have been uploaded with provenance metadata.
Attestation for enola_cli-0.4.33-py3-none-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
