Pulse
2026-09-18-v3.0
Dataset
2026-10-27-catalog-ai-v2
Ruleset
b2e8889c66f7
Scanned
2026-10-27
Window
February–September 15, 2026
Catalog tracking observation. This repository is measured with the same fixed window and ruleset, but it is not part of the published benchmark or its aggregate claims.

PC 端语音输入工具,离线识别,高准确率、低延迟,支持热词、LLM润色。按住CapsLock或鼠标侧键X2说话,松开自动上屏。

HaujetZhao/CapsWriter-Offline ↗

HaujetZhao/CapsWriter-Offline AI coding statistics: 0%

of 249 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate

No signed agent commits found

No agent signatures were found in the last 249 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.

0
agent commits
249
other considered commits
—
agent contributors
—
largest contributor

What shapes this result

Mode, timing, and detected signatures show whether the result reflects broad adoption or one concentrated workflow.

No agent signatures were detected, so there are no agent, mode, or timing drivers to break down.

Inspect the matches

Public commit samples let you inspect the signatures behind the aggregate result.

No matched commit samples are available for this observation.

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 window249
Merge commits removed−0
CI / dependency bots removed−0
Considered249

Bots are excluded from the denominator entirely. Agent attribution requires a literal supported signature; no code-style inference is used.

Reproduce this observation

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 HaujetZhao/CapsWriter-Offline

Scan another repository