Asqav Claude Code

Asqav receipts for Claude Code

Signed evidence of what your coding agent did.

This plugin watches a Claude Code session through hooks and, when the session stops, signs one Asqav `code_authorship` receipt summarizing it: which files changed (content hashes before and after), which commands ran (hashed), and the git context. The receipt is cryptographically signed, timestamped, and verifiable by anyone with the link.

Teams adopting Claude Code are being asked for an audit trail of AI-generated code. The EU AI Act's record-keeping obligations for high-risk systems apply from 2 December 2027, and from 2 August 2028 for those classified under Annex I, after Regulation (EU) 2026/1744 replaced the applicability dates in Article 113; SOC 2 auditors already ask how production code gets written today. A log file you can edit is weak evidence. A signed receipt is not.

Quickstart (about 5 minutes)

1. Create an Asqav account and an agent at [asqav.com/dashboard](https://asqav.com/dashboard), and copy an API key. The free tier covers this.

2. Export the credentials:

export ASQAV_API_KEY=sk_...
export ASQAV_AGENT_ID=agt_...

1. Install the plugin. Either load it directly:

git clone https://github.com/jagmarques/asqav-claude-code.git
claude --plugin-dir ./asqav-claude-code

or paste the hooks block from [`examples/settings-snippet.json`](examples/settings-snippet.json) into your `.claude/settings.json` (fix the script path first).

1. Run a Claude Code session inside a git repository. Edit a file, run a command, then stop the session. Claude Code shows the receipt as a system message:

asqav: signed code_authorship receipt sig_... verify at https://asqav.com/verify/sig_...

1. Open the verify URL. That page is public, so you can hand it to a reviewer or an auditor as is.

Requirements: Python 3.10+, git, and network access to `api.asqav.com`. No pip packages needed. If the `asqav` Python SDK happens to be installed, the hook signs throu