Engineering Tooling
EVAGIX
Claims → local evidence → deterministic findings.
Validates repository claims and agent-facing guidance against local evidence, producing deterministic findings for developers and CI.
Problem
Repository documentation and agent-facing instructions can drift away from the code and configuration they describe, creating false confidence for developers, CI, and coding agents.
Approach
- Collects repository-local evidence from documentation, manifests, workflows, configuration, command definitions, and agent-facing context.
- Validates claims and guidance with deterministic rules, repository policy, and explicit evidence boundaries rather than treating prose as trusted truth.
- Produces reviewable findings through CLI, JSON, SARIF, and CI-friendly outputs while remaining local-first and dependency-light.
Signals & Results
- Validation evidence: tested across 100+ repositories spanning diverse technology stacks.
- Published Python CLI with PyPI distribution, CI, documentation, security guidance, and JSON / SARIF outputs.
- Explicit scope boundary: static repository evidence complements tests, code review, SAST, secret scanning, and runtime verification rather than replacing them.
Stack
Project media
EVAGIX validating repository claims against local evidence
