Getting Started
Codevidence docs
Codevidence links compliance controls to the exact code that implements them, and generates structured evidence in your build. This reference covers what’s shipping today — Declared (from an annotation) and Verified (from a test) — and what’s still in design: Observed.
Start here
- Installation — add the Maven or Gradle plugin.
- Quickstart — annotate a method, run your build, verify it with a test.
- The evidence model — Declared, Verified, Observed, and why the difference matters.
- The portal & evidence API — publish records to Codevidence and review controls against the code In preview.
The three evidence tiers
| Tier | Status | Description |
|---|---|---|
Declared |
Available now | A developer annotated the code. The build plugin extracted that fact from compiled bytecode. |
Verified |
Available now | A JUnit test called a typed compliance assertion, and Codevidence recorded whether it passed or failed. |
Observed |
In design | Runtime instrumentation confirms the control executed in production. See the roadmap page. |
Reference sections
-
Reference — Declared
Available now
— the
@ComplianceControlannotation, supported frameworks, the evidence record schema, and build plugin configuration. -
Reference — Verified
Available now
— the
@VerifiesControlannotation, the assertion library, and the verified evidence record schema.
New to the product? Read Why bytecode, not source next — it's the architectural constraint everything else here is built around.