The audit trail for AI-written code.
Zicodera Attesta records who — or what — wrote each change, under which policy, and who reviewed it. Verifiable evidence for auditors, customers, and your own engineering leadership.
Designed to collect metadata and hashes, not source code.
PR-2041 · payments-api
Add idempotency keys to refund endpoint
Commit
DeclaredCommit by m.okafor touching 1 file
AI session
AttestedUsed: Code assistant
Review
AttestedApproved by s.tanaka
CI
AttestedChecks passed
Merge
AttestedMerged to main in payments-api
Hover or focus a node to see the event, its tier, and its hash. Signatures are simulated. Sample data.
Provenance coverage
75%
Attested 5 · Declared 4 · Inferred 3. Inferred is not counted.
Policy failing
3
of 12 changes
Passing all policies
75%
of 12 changes
| Change | Repository | Tier | Review | Policy |
|---|---|---|---|---|
| PR-2041Add idempotency keys to refund endpoint | payments-api | Attested | Human review | Pass |
| PR-2043Retry backoff for settlement job | payments-api | Attested | Automated only | Pass |
| PR-2047Refactor currency rounding helpers | payments-api | Declared | Automated only | Pass |
| PR-2050Fix webhook signature comparison | payments-api | Inferred | Human review | Pass |
| PR-2052Hotfix: null guard in ledger export | payments-api | Inferred | No review | Fail |
| PR-2055Checkout form validation messages | web-app | Attested | Human review | Pass |
PR-2041 · payments-api
Add idempotency keys to refund endpoint
AttestedHuman review PassPR-2043 · payments-api
Retry backoff for settlement job
AttestedAutomated only PassPR-2047 · payments-api
Refactor currency rounding helpers
DeclaredAutomated only Pass
Your codebase has a new author. Your records don't.
Customers, auditors, and leadership are starting to ask how AI is used in software delivery. Today the answers often live in memory and chat threads.
- Unknown
Which repositories use AI assistants or agents?
- Unknown
Which models and tools touched this change?
- Unknown
Who reviewed it, and under which policy?
One ledger. Every tool. Verifiable.
Attesta captures provenance signals from your git host, CI, and AI tooling, writes them to a tamper-evident ledger, evaluates your policies, and turns the result into evidence you can hand to an auditor.
What Attesta does
Six capabilities, each labelled with where it stands today.
- Provenance ledgerPreviewEvery event hash-chained and checkpointed, so tampering is detectable.
- Confidence tiersPreviewAttested, Declared, Inferred. Certainty is always shown, never hidden.
- Policy enginePreviewRules like "human review required on sensitive paths," tested against history before enforcement.
- Tool & model inventoryPreviewSee which AI tools and models are actually in use across repositories.
- Evidence packsPreviewPeriod-scoped, verifiable exports for audits and customer reviews.
- Questionnaire assistantPlannedDraft answers that cite ledger events.
Connect, capture, prove
Three steps from a read-only install to an evidence pack.
- 1
Connect
Install the read-only git app. It collects metadata only.
- 2
Capture
Add the CI attestation step. Route AI tools through Gateway when available.
- 3
Prove
Review coverage, enforce policy, export an evidence pack.
# Illustrative — interface subject to change
- name: Attest change provenance
uses: zicodera/attesta-action@v1
with:
tier: attestedTry it: explore sample changes
Filter the sample changes, switch a policy on and off, open a change, and verify its ledger. Everything here runs in your browser on fictional sample data.
Built for the questions you are being asked
Five situations, and the artifact Attesta produces for each.
Customer security questionnaires
Situation
A customer's security review asks whether AI coding tools are used, which ones, and how output is reviewed. The answer today is assembled from memory and chat threads.
What Attesta provides
- A current inventory of tools and models, backed by recorded events
- Review-coverage figures you can quote and trace
- A drafting assistant whose answers cite ledger eventsPlanned
Output
- Question
- Do you use AI coding assistants?
- Answer (draft)
- Yes, in 3 of 4 repositories, from an approved list.
- Evidence
- 42 ledger events · 31 Attested · 11 Declared
- Sample data
- Illustrative excerpt, not real figures
Fits the tools you already use
Only GitHub is in preview today. Everything else is planned, and we label it that way.
- GitHubPreview
- GitLabPlanned
- BitbucketPlanned
- Azure DevOpsPlanned
- GitHub ActionsPlanned
- JenkinsPlanned
- JiraPlanned
- SlackPlanned
- OktaPlanned
- SnykPlanned
Product names are trademarks of their respective owners. Listing a name here describes a planned or preview integration and does not imply endorsement, partnership, or certification by the owner.
Your source code stays yours.
Four design principles shape how Attesta handles your data.
Metadata-only collection by design
Hash-chained ledger with signed checkpoints
Least-privilege, read-only app scopes
Regional storage and SSO/SCIM
Planned
Start free. Pay per active contributor.
Launch pricing for private preview.
Free
$0
For trying Attesta on a small set of repositories.
Up to 5 contributors, 3 repositories
Team
$15per active contributor / month
For engineering teams that need policy checks and evidence.
Minimum 10 contributors
Business
$29per active contributor / month
For organisations with audit, security, and customer-review obligations.
Minimum 25 contributors
Enterprise: custom pricing for large or regulated organisations. Talk to us.
Pricing may change during private preview.