evagix 0.1.0__tar.gz

evagix-0.1.0/CHANGELOG.md

@@ -0,0 +1,27 @@
+# Changelog
+
+All notable user-facing changes to Evagix are documented here.
+
+## [0.1.0]
+
+First public release.
+
+### Added
+
+- Local-first repository classification, readiness checks, and explainable findings.
+- README claim auditing against static repository evidence.
+- Agent-context discovery, safety analysis, scoring, and generated context exports.
+- Generated-context ownership, fingerprint, integrity, drift, and tamper checks.
+- CI workflow generation, changed-file risk analysis, and PR-oriented reports.
+- JSON, Markdown, SARIF, annotation, and machine-readable report formats.
+- Python, Node.js, GitHub Actions, container, infrastructure, and AI/ML repository evidence.
+- Packaged JSON schemas for stable machine-readable outputs.
+
+### Important behavior
+
+- Scans are static and do not execute project commands, install dependencies, call model APIs, or upload repository content.
+- Risky generated commands and unsafe output paths are rejected conservatively.
+- Ambiguous evidence is reported for review rather than treated as verified truth.
+- The package supports Python 3.11 through 3.14 and has no runtime dependencies.
+
+[0.1.0]: https://github.com/tarekmasryo/Evagix/releases/tag/v0.1.0

evagix-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Tarek Masryo
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

evagix-0.1.0/MANIFEST.in

@@ -0,0 +1,11 @@
+include README.md
+include LICENSE
+include CHANGELOG.md
+include SECURITY.md
+include evagix/py.typed
+recursive-include evagix/schemas *.json
+
+prune tests
+
+global-exclude *.py[cod]
+global-exclude CACHEDIR.TAG

evagix-0.1.0/PKG-INFO

@@ -0,0 +1,454 @@
+Metadata-Version: 2.4
+Name: evagix
+Version: 0.1.0
+Summary: Local-first evidence gate for AI-assisted repositories.
+Author: Tarek Masryo
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/tarekmasryo/Evagix
+Project-URL: Repository, https://github.com/tarekmasryo/Evagix
+Project-URL: Issues, https://github.com/tarekmasryo/Evagix/issues
+Project-URL: Changelog, https://github.com/tarekmasryo/Evagix/blob/main/CHANGELOG.md
+Project-URL: Security, https://github.com/tarekmasryo/Evagix/blob/main/SECURITY.md
+Keywords: agents,ai-agents,repo-governance,context-engineering,evidence-gate,agent-context,cli,developer-tools,ci,repo-analysis
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: setuptools==83.0.0; extra == "dev"
+Requires-Dist: wheel==0.47.0; extra == "dev"
+Requires-Dist: pytest==9.1.1; extra == "dev"
+Requires-Dist: pytest-cov==7.1.0; extra == "dev"
+Requires-Dist: ruff==0.15.20; extra == "dev"
+Requires-Dist: mypy==2.1.0; extra == "dev"
+Requires-Dist: build==1.5.0; extra == "dev"
+Requires-Dist: twine==6.2.0; extra == "dev"
+Requires-Dist: jsonschema==4.26.0; extra == "dev"
+Provides-Extra: security
+Requires-Dist: pip-audit==2.10.1; extra == "security"
+Dynamic: license-file
+
+<h1 align="center">Evagix</h1>
+
+<p align="center">
+  <strong>Local-first evidence validation for AI-assisted repositories.</strong>
+</p>
+
+<p align="center">
+  Evagix checks repository claims, documented commands, agent-facing instructions,
+  and generated context against local evidence before humans or coding agents rely on them.
+</p>
+
+<p align="center">
+  <a href="https://pypi.org/project/evagix/">
+    <img alt="PyPI version" src="https://img.shields.io/pypi/v/evagix">
+  </a>
+  <a href="https://github.com/tarekmasryo/Evagix/actions/workflows/ci.yml">
+    <img alt="CI" src="https://github.com/tarekmasryo/Evagix/actions/workflows/ci.yml/badge.svg">
+  </a>
+  <img alt="Python" src="https://img.shields.io/badge/python-3.11--3.14-blue">
+  <img alt="Runtime dependencies" src="https://img.shields.io/badge/runtime%20dependencies-0-brightgreen">
+  <a href="https://github.com/tarekmasryo/Evagix/blob/main/LICENSE">
+    <img alt="License" src="https://img.shields.io/badge/license-Apache--2.0-blue">
+  </a>
+</p>
+
+<p align="center">
+  <a href="#quick-start">Quick start</a>
+  ·
+  <a href="#core-commands">Commands</a>
+  ·
+  <a href="https://github.com/tarekmasryo/Evagix/tree/main/docs">Documentation</a>
+  ·
+  <a href="https://github.com/tarekmasryo/Evagix/blob/main/SECURITY.md">Security</a>
+</p>
+
+<p align="center">
+  Evagix v0.1.0 provides conservative local evidence checks and
+  CI-friendly repository validation.
+</p>
+
+---
+
+## Why Evagix?
+
+AI-assisted development increasingly depends on repository text: README files, agent instructions, CI notes, generated context, and documented commands.
+
+Those instructions can drift away from the repository they describe.
+
+```text
+README says: npm test
+package.json has no matching test script
+```
+
+```text
+README claims Docker support
+no Dockerfile or Compose file exists
+```
+
+```text
+AGENTS.md documents one test command
+evagix.toml declares another
+```
+
+Evagix treats repository instructions as evidence-backed artifacts rather than trusted prose.
+
+```text
+repository evidence
+        ↓
+rules + policy
+        ↓
+findings + scoring
+        ↓
+text / JSON / Markdown / SARIF
+```
+
+It is intentionally focused: Evagix validates repository-facing evidence and instructions. It does not replace tests, CI, code review, SAST, secret scanning, or dependency auditing.
+
+---
+
+## Quick start
+
+Install:
+
+```bash
+python -m pip install evagix
+```
+
+Run the main checks:
+
+```bash
+evagix doctor . --strict --fail-under 80
+evagix readme-audit . --strict --fail-on unsupported
+evagix eval-context . --strict --fail-on high
+evagix check .
+```
+
+The shorter `evgx` command is also available:
+
+```bash
+evgx doctor .
+```
+
+---
+
+<!-- evagix:audit-ignore-start -->
+
+## Typical findings
+
+| Finding | Why it matters |
+| --- | --- |
+| README claims Docker support, but no Dockerfile or Compose file was found. | Prevents unsupported setup claims from being treated as repository fact. |
+| README documents `npm test`, but no matching package script exists. | Flags stale commands before humans or agents copy them. |
+| `AGENTS.md` and `evagix.toml` disagree about the canonical test command. | Surfaces conflicting agent instructions. |
+| Generated context fingerprint no longer matches repository facts. | Detects context drift. |
+| Agent-facing docs instruct tools to read local environment files. | Flags risky guidance around local secrets. |
+| CI is claimed in documentation, but no workflow evidence exists. | Prevents readiness claims from being inferred without evidence. |
+
+<!-- evagix:audit-ignore-end -->
+
+---
+
+## Install
+
+### PyPI
+
+```bash
+python -m pip install evagix
+```
+
+For an isolated CLI installation:
+
+```bash
+pipx install evagix
+```
+
+Upgrade with:
+
+```bash
+python -m pip install --upgrade evagix
+```
+
+or:
+
+```bash
+pipx upgrade evagix
+```
+
+### From source
+
+```bash
+git clone https://github.com/tarekmasryo/Evagix.git
+cd Evagix
+python -m pip install -e ".[dev]"
+```
+
+Check the CLI:
+
+```bash
+evagix --version
+evgx --version
+```
+
+Evagix requires **Python 3.11 or newer** and has **zero runtime dependencies**.
+
+The release CI matrix validates Python 3.11, 3.12, 3.13, and 3.14. Newer interpreter versions are considered supported only after they enter that matrix.
+
+---
+
+## What Evagix checks
+
+Evagix works from repository-local evidence.
+
+| Area | What it looks for |
+| --- | --- |
+| README evidence | Unsupported or weakly supported claims about tests, CI, Docker, packaging, deployment, typing, monitoring, and related capabilities |
+| Commands | Install, test, lint, typecheck, build, eval, smoke, and application-run evidence |
+| Agent context | `AGENTS.md`, supported tool-specific context files, conflicts, unsafe instructions, and missing canonical commands |
+| Generated context | Missing, stale, unmanaged, tampered, truncated, or invalid generated targets |
+| Safety signals | Dangerous shell guidance, credential-bearing commands, environment exposure, and context-poisoning patterns |
+| Repository signals | Languages, tests, migrations, tooling, infrastructure markers, and related readiness evidence |
+| CI / PR context | Workflow evidence and advisory changed-file risk signals |
+
+Findings are designed to explain what was detected, what evidence supports it, why it matters, and what should be fixed or deliberately waived.
+
+See the complete [`rule reference`](https://github.com/tarekmasryo/Evagix/blob/main/docs/rules-reference.md).
+
+---
+
+## Core commands
+
+| Goal | Command |
+| --- | --- |
+| Repository readiness | `evagix doctor . --strict --fail-under 80` |
+| README evidence audit | `evagix readme-audit . --strict --fail-on unsupported` |
+| Agent-context evaluation | `evagix eval-context . --strict --fail-on high` |
+| Generated-context verification | `evagix check .` |
+| Generate context | `evagix compile . --force` |
+| Preview synchronization | `evagix sync . --plan` |
+| Repository audit | `evagix audit .` |
+| PR risk signals | `evagix pr-risk . --base main` |
+| Explain a finding | `evagix explain missing-ci` |
+| Export a report | `evagix report .` |
+
+Additional commands for baselines, scoped checks, context packs, evidence export, and automation are documented in [`docs/commands.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/commands.md).
+
+`--strict` enables stricter gate behavior. Failure thresholds are controlled by command-specific options such as `--fail-under`, `--fail-on high`, and `--fail-on unsupported`.
+
+`pr-risk` is advisory and does not replace repository checks, tests, CI, or human review.
+
+### Advanced commands
+
+| Goal | Command |
+| --- | --- |
+| Baseline snapshot | `evagix baseline .` |
+| Baseline diff | `evagix diff .` |
+| Scoped checks | `evagix scoped .` |
+| Context pack | `evagix context-pack .` |
+
+---
+
+## How it works
+
+```mermaid
+flowchart LR
+    A[Repository files] --> B[Evidence collection]
+    B --> C[Rules and policy]
+    C --> D[Findings and scoring]
+    D --> E[Reports and generated context]
+
+    B --> B1[README claims]
+    B --> B2[Commands]
+    B --> B3[Agent context]
+    B --> B4[CI and repository signals]
+
+    E --> E1[Text]
+    E --> E2[JSON]
+    E --> E3[Markdown]
+    E --> E4[SARIF]
+```
+
+Evagix does **not** execute project commands while scanning, install project dependencies, call model APIs, or upload the repository.
+
+Static markers are evidence signals, not proof of high-impact claims such as `secure` or `production-ready`. When local evidence is insufficient, Evagix keeps the result weak, partial, unsupported, or subject to manual review instead of manufacturing certainty.
+
+---
+
+## Reports and outputs
+
+```bash
+evagix doctor . --format json
+evagix readme-audit . --format json
+evagix eval-context . --format json
+evagix report . --format sarif --output evagix.sarif --force
+```
+
+| Format | Typical use |
+| --- | --- |
+| Text | Local review |
+| JSON | Automation and CI parsing |
+| Markdown | Human-readable reports |
+| SARIF | Code-scanning style integrations where supported |
+
+Evidence-sensitive reads are bounded. Truncated, unreadable, or invalid UTF-8 input is reported as incomplete rather than being treated as clean evidence.
+
+---
+
+## CI usage
+
+A conservative CI gate can run:
+
+```bash
+python -m evagix check .
+python -m evagix doctor . --strict --fail-under 80
+python -m evagix readme-audit . --strict --fail-on unsupported
+python -m evagix eval-context . --strict --fail-on high
+```
+
+For gradual adoption, start with reporting-only output, review the findings, then add strict thresholds when the repository policy is ready to enforce them.
+
+---
+
+## Configuration
+
+`evagix.toml` defines canonical commands, generated targets, and policy thresholds.
+
+```toml
+[policy]
+fail_on_stale = true
+fail_under = 80
+
+[commands]
+test = "python -m pytest"
+lint = "python -m ruff check ."
+typecheck = "python -m mypy evagix"
+```
+
+Configuration is validated before it is trusted. Invalid keys, empty commands, unsafe target paths, literal command credentials, and high-risk shell commands are rejected at the relevant boundary.
+
+README examples can be excluded from claim analysis, while intentionally waived real claims remain visible in results.
+
+See [`docs/configuration.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/configuration.md).
+
+---
+
+## Generated context
+
+Evagix can create opt-in agent-facing context for `AGENTS.md`-compatible workflows and supported tool-specific targets.
+
+Neutral Evagix-managed context targets include:
+
+```text
+.evagix/context.md
+.evagix/context.json
+```
+
+Generated context carries ownership and fingerprint information.
+
+Evagix records integrity state separately in:
+
+```text
+.evagix/integrity.json
+```
+
+This allows `evagix check` to detect stale context and manual modification independently, and to report both when appropriate.
+
+Tool-specific exports are generated only when explicitly requested or configured. Vendor names identify compatible target formats only; they do not imply affiliation, endorsement, or sponsorship.
+
+---
+
+## Conservative behavior
+
+Evagix intentionally avoids turning missing evidence into confidence:
+
+- External or missing agent context is unscored rather than receiving a positive structural score.
+- Incomplete README reads do not become clean `100/100` results.
+- Invalid UTF-8 and unsafe path conditions are surfaced instead of silently ignored.
+- Generated context freshness and integrity are checked independently.
+- Unsafe repository-internal symlink traversal is rejected.
+- Policy waivers remain visible and do not create supporting evidence.
+
+Exact semantics are documented in the [`rule reference`](https://github.com/tarekmasryo/Evagix/blob/main/docs/rules-reference.md).
+
+---
+
+## Supported environments
+
+Evagix targets Python **3.11–3.14** through its release matrix.
+
+It has zero runtime dependencies and does not require network access for repository scans.
+
+Evagix can inspect repositories containing different languages and ecosystems, but it is not a deep language or framework analyzer.
+
+---
+
+## Scope
+
+Evagix is not:
+
+- a full security scanner;
+- a secret scanner;
+- a dependency vulnerability auditor;
+- a semantic code analyzer;
+- a test runner;
+- a CI replacement;
+- a release approval system.
+
+It complements those tools by checking whether repository-facing instructions and claims are supported by local evidence available to humans and coding agents.
+
+---
+
+## Documentation
+
+| Document | Purpose |
+| --- | --- |
+| [`docs/architecture.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/architecture.md) | Architecture boundaries and extension rules |
+| [`docs/commands.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/commands.md) | Command guide and common workflows |
+| [`docs/configuration.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/configuration.md) | Configuration reference |
+| [`docs/rules.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/rules.md) | Rule overview |
+| [`docs/rules-reference.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/rules-reference.md) | Complete rule reference |
+| [`docs/schemas.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/schemas.md) | JSON schema notes |
+| [`SECURITY.md`](https://github.com/tarekmasryo/Evagix/blob/main/SECURITY.md) | Security policy |
+| [`CONTRIBUTING.md`](https://github.com/tarekmasryo/Evagix/blob/main/CONTRIBUTING.md) | Contribution workflow |
+
+---
+
+## Development
+
+```bash
+python -m pip install -e ".[dev]"
+python -m ruff check .
+python -m ruff format --check .
+python -m mypy evagix
+python -m pytest --cov=evagix --cov-branch --cov-report=term-missing --cov-fail-under=80
+```
+
+Architecture boundaries are documented in [`docs/architecture.md`](https://github.com/tarekmasryo/Evagix/blob/main/docs/architecture.md).
+
+---
+
+## Security
+
+Evagix is designed to inspect repository evidence conservatively and avoid unnecessary access to known secret-bearing file types.
+
+It does not intentionally read `.env` files or private-key formats as ordinary repository evidence.
+
+For vulnerability reporting and security policy, see [`SECURITY.md`](https://github.com/tarekmasryo/Evagix/blob/main/SECURITY.md).
+
+---
+
+## License
+
+Apache-2.0. See [`LICENSE`](https://github.com/tarekmasryo/Evagix/blob/main/LICENSE).