gitvow scan reads git log and nothing else. It writes nothing, sends nothing, needs no configuration, and works on a repository that has never heard of gitvow. Run it in any repository where agents have been working.
What each line means
reverts and the first touched a gated file line are the diagnostic, counted over every commit whoever made it: how often this history undoes itself, and how much of its change the policy in force would have seen at all. On most repositories the second number is small. When it is under one percent of a history of any size, the page says so in words: the default rules are a starting point, never a claim about where this repository’s consequence lives. Learning where it does live is a separate, paid run over the whole estate. agent-assisted counts commits whose message carries an agent’s own signature: a co-author trailer from Claude Code, Cursor, Copilot, Codex, Gemini, Devin, Aider, Factory or Windsurf, the “Generated with Claude Code” line, or aGitvow-Session trailer from gitvow itself. The agents named are the ones it found.
touched a gated file counts those commits that changed a file matching a path_confirm rule, so the definition comes from your own policy where you have one and from the default otherwise. The output says which it used.
recorded who agreed counts those that carry a Gitvow-Accepted or Gitvow-Declined trailer. On a repository without gitvow this is zero by construction, which is the point of running it.
An open finding, if any, is a commit made by a person while an agent’s finding was still unanswered.
What it will not tell you
The count is a floor, not a total. An agent that leaves no trailer in the commit message is invisible to this scan, and plenty do not leave one. Once gitvow is installed it does not rely on trailers: the session is recorded from the hook, whether the agent signs its work or not. It also says nothing about whether those commits were correct. A commit that changed an authorization file with nobody’s judgment attached may have been completely right. The scan tells you that the judgment was not recorded, not that it was absent.Is the record complete?
Gitvow-Session trailer is a coverage hole: that machine was never configured, or its hooks were disabled for that command. Coverage is computed from history alone, so it trusts no client and cannot be improved by deleting anything locally.
--who exists to find that machine, not to rank the person. And it is a floor, not a total, for the same reason the scan is: an agent that signs nothing at all is invisible to it. A session is recorded from the hook whether or not the agent signs its commits, so coverage understates a healthy install and never overstates it.
Why this matters more than deletion. The record lives inside your commits, so it is exactly as durable as the code it describes. What a laptop can do is never produce a record in the first place, and coverage is how you see that from the outside. Put gitvow coverage --fail-under in the pull request check and the hole closes.