Docket: Open-source tool released to manage evidence records of AI agent code generation on a per-commit basis
Key point
Docket, an open-source CLI tool, has been released to record the verification history of code generated by AI coding agents on a per-commit basis and to guide reviewer attention.
Details
The GitHub repository Dillonsmart/docket is a Go-based CLI tool designed to address the issue where the implementation process and verification records of code generated by AI coding agents disappear at the time of commit. Docket captures the agent's work journey, merges it with the diff, and generates evidence records per hunk to help reviewers focus on parts lacking evidence.
Core Features and Working Principles
- Evidence Recording and Verification: Records are stored in an orphan ref within the repository without relying on networks or external accounts. The
docket showcommand allows users to check the trust status (local_claimed, ci_attested) and evidence density per hunk. - Attribution Mechanism: It parses Agent transcripts into an event stream, performs file-specific edit replay, and tracks line-level provenance vectors. At commit time, hunks are sorted to clarify the origin of code changes.
- Evidence Density Calculation: Scores are calculated by summing Coverage (max 0.5), checks passed after edit (0.3), type/static checks (0.1), and human contact (0.1). Caps are applied to prevent score inflation when there is no code execution or the author is unclear.
Performance and Support Scope
Docket supports Claude Code, Codex CLI, and opencode, with the underlying logic being agent-agnostic. Performance measurements via docket gate showed that Claude Code (Laravel) achieved high attribution accuracy with Hunk 98.1% and Added lines 99.8%. Conversely, in environments with many shell-based edits, Hunk accuracy dropped to 59.2%, revealing the limitations of transcript recording.
Security and Privacy
To prevent secret exposure and infinite repository growth, only redacted excerpts are stored instead of full transcripts. Credentials, JWTs, etc., undergo aggressive redaction, and data is stored in the local repository. Upon docket push, data is transmitted to the git host, and signing keys are stored in .git/docket/. The Commit Evidence Record (CER) spec is released under the Apache 2.0 license.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.