Provenance

A quarter of vLLM’s last three hundred commits carry an agent’s name

One of them is signed off by codex@openai.com. The Developer Certificate of Origin that signature satisfies was written to be signed by a person, and vLLM’s contributing rules do not mention agents at all.

No agent signal 224 Codex 39 Claude 30 Cursor and other bots 7
The last 300 commits on vLLM’s main branch, 31 August to 7 September 2026, classified by the authorship trailer in the commit message. Each commit counted once.

Commit d2906cc landed on vLLM’s main branch on 4 September carrying two trailers: “Generated-by: Codex <codex@openai.com>” and “Signed-off-by: Codex <codex@openai.com>”. The second line is a Developer Certificate of Origin sign-off, and vLLM requires one on every commit.

The DCO is not a formality. It is the contributor asserting they have the right to submit the code under the project’s licence, and here that assertion is made by a mailbox.

Across the last 300 commits on main, from 31 August to 7 September, 76 carry an agent authorship signal: 39 name Codex, 30 carry a Co-Authored-By line for Claude, and 7 name Cursor or another bot, against 224 with no such signal. The Claude and Cursor commits are mostly co-authorship trailers on work a named human signed off, which is a different thing from a bot signing alone. The Codex commits are the ones where the certifying identity is the tool.

vLLM’s rules say nothing about any of this. CONTRIBUTING.md at the repository root is one sentence pointing at the documentation site. The pull-request template asks for a purpose, a test plan and a test result. The DCO file is the standard text. None of the three mentions AI-generated contributions, and there is no requirement to disclose them, which means the 39 commits that do disclose are volunteering the information.

The commit itself is small and looks right. It threads a CPU-side query_lens_cpu tensor through prefill metadata so the TRT-LLM ragged attention kernel stops re-deriving sequence lengths from a GPU tensor on every forward pass, which is what was forcing a synchronisation on the prefill hot path. Of its 54 insertions, 47 are new tests and 7 are the fix.

What is missing is the review trail. No pull request is associated with that commit through the GitHub API, and a title search returns none, so the commit reached main authored by Codex and committed two hours later by khluu, a vLLM release maintainer, with a green CI run and no discoverable human review comment. A separate pull request, numbered 55499 and still open, proposes a related fix; it has drawn two bot comments against no submitted human review. Whether a human read d2906cc somewhere off GitHub cannot be established from the public record, which is the point: the public record is what the DCO exists to create.

None of this says the patch is wrong. It says that the mechanism a reader would use to find out who stands behind it now resolves to an email address at the company that wrote it.

vLLM sits under a large share of production inference. The question its maintainers have not had to answer in writing is whether a certificate of origin signed by a tool is a certificate at all.

What it changes If your compliance process treats a DCO sign-off as provenance for a dependency, that assumption is now partly false for vLLM and probably for others. Check what your own contribution rules say about agent-authored commits before someone asks you.

Primary source read

Published in the edition of Monday, 7 September 2026 · Beat: Infrastructure