Aegis
A deterministic validator for AI-generated code. Apache 2.0.
What it does
aegis check ./path runs a 24-layer pipeline against a directory of
code and reports whether the validation passes. Layers cover AST
parsing, import resolution, cross-file consistency, package install,
type check, test execution, design-brief fidelity, and feature
coverage. 22 layers are deterministic (no model call); 1 is LLM-judge;
1 is hybrid (LLM verdict with a deterministic override).
Install
Install from source (a published pip install aegis-validator package is
coming soon):
git clone https://github.com/andraste-labs/aegis.git
cd aegis
pip install -e .
The Anthropic SDK is an optional extra for the LLM-using layers:
pip install -e ".[anthropic]"
Quick start
aegis check ./my-code # deterministic + LLM
aegis check ./my-code --no-llm # deterministic only
aegis check ./my-code --brief brief.json # include design / feature layers
aegis check ./my-code --json report.json # machine-readable report
aegis check ./my-code --exit-on-fail # exit 1 on FAIL
The LLM-using layers (design_fidelity, feature_coverage) skip
unless an ANTHROPIC_API_KEY is set and a brief.json is supplied.
Layers
See docs/LAYER_INDEX.md for the full list
of layers, their kinds (deterministic / hybrid / llm_judge), and the
file under aegis/checks/ that implements each one.
Benchmark
aegis-bench/ contains a cohort of reproducible cases. Each case has
a brief.json, an input/ directory, an expected.json describing
the validator output, and a short technical README.
python -m aegis_cli check aegis-bench/cohort/<case>/input \
--brief aegis-bench/cohort/<case>/brief.json \
--no-llm
See aegis-bench/METHODOLOGY.md for
case structure and reproducibility rules.
Contributing
See CONTRIBUTING.md.
License
Maintainer
Aegis is maintained by Andraste Labs. Contact: github@andrastelabs.com.
Metadata
Release files for aegis-validator 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aegis_validator-0.1.0.tar.gz | 157.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aegis_validator-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 268.2 kB
Release files / aegis_validator-0.1.0.tar.gz
| Download URL | aegis_validator-0.1.0.tar.gz |
|---|---|
| Size | 157.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
084be19ea65fa8493b64917cf7153b4a8fdbc4d021e0989b062d87b3721b3e9c
|
|
BLAKE2b-256 checksum How to use checksums |
7196949d808792a96b5a85c9ea578b5858a7b4af80754b3cc56c4a9471d2e492
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.0
|
Release files / aegis_validator-0.1.0-py3-none-any.whl
| Download URL | aegis_validator-0.1.0-py3-none-any.whl |
|---|---|
| Size | 110.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee0e2e3047c48c24823219302fb2ef073358dbcffe0edaf4ef6c314560d15d5e
|
|
BLAKE2b-256 checksum How to use checksums |
774d2333c7cc9e6d693a8586b932fa83d45d9ed22c85ede0803ff18828d4e515
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.0
|
Security for aegis-validator 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.