- Dataset
- 2026-10-27-catalog-ai-v2
- Ruleset
- b2e8889c66f7
- Scanned
- 2026-10-27
- Window
- February–September 15, 2026
Self-hosted AI gateway for multi-channel, multi-credential setups — API keys and subscription accounts, scheduling, failover, request logs and usage. 自托管 AI 网关:多渠道多凭据统一接入,含密钥与订阅账号、调度容错、日志与用量。
01Result
tbphp/gpt-load ↗tbphp/gpt-load AI coding statistics: 0%
No signed agent commits found
No agent signatures were found in the last 768 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.
03Evidence
Inspect the matches
Public commit samples let you inspect the signatures behind the aggregate result.
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 | 817 |
| Merge commits removed | −41 |
| CI / dependency bots removed | −8 |
| Considered | 768 |
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 tbphp/gpt-load