- Dataset
- 2026-10-27-catalog-ai-v2
- Ruleset
- b2e8889c66f7
- Scanned
- 2026-10-27
- Window
- February–September 15, 2026
Portable AI agent runtime for the JVM. One @Agent class runs on Spring AI, LangChain4j, Anthropic, or 9 more behind one SPI. Token streaming, tool calls, human approvals, and governance over WebSocket, SSE, gRPC, or WebTransport/HTTP3. Speaks MCP, A2A, and AG-UI.
01Result
Atmosphere/atmosphere ↗Atmosphere/atmosphere AI coding statistics: 0%
No signed agent commits found
No agent signatures were found in the last 2,363 considered commits. That is a real result, not a failure to measure.
It does not mean no AI was used here. A developer can use an agent and commit by hand without leaving a detectable git signature.
02Drivers
What shapes this result
Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.
Which agents
| Agent | Vendor | Commits | Share |
|---|---|---|---|
| Claude Code | Anthropic | 1 | 0% |
03Evidence
Inspect the matches
Public commit samples let you inspect the signatures behind the aggregate result.
Matched commit samples
22e50d8fon GitHubtest(e2e): implement 5-gap E2E test expansion proposal CLI runtime tests, Claude Code
04Method
What entered the denominator
The result begins with commit history, removes merges and routine automation, and reports literal agent signatures as a lower bound.
Exclusion ledger
| Commits in window | 2,443 |
| Merge commits removed | −26 |
| CI / dependency bots removed | −54 |
| Considered | 2,363 |
Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.
Continue exploring
Related coding-agent evidence
Run the same detector locally.
Deterministic signature matching; no code-style inference. Squash merges can remove trailers, so this result remains a measured floor.
npx qmmit-cli Atmosphere/atmosphere