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.

持续维护的企业面试题库网站，帮你拿到满意 offer！⭐️ 2026年最新Java面试题、前端面试题、AI大模型面试题、AI Agent面试题、RAG面试题、C++面试题、Go面试题、Python面试题、测试面试题、运维面试题、后端面试题、操作系统面试题、计算机网络面试题、Redis面试题、MySQL数据库面试题、算法面试题、Spring面试题、JVM面试题、Java并发面试题、Linux面试题、LLM面试题、Prompt工程面试题、系统设计面试题等1万多道高频程序员求职必备八股文。面试刷题就选面试鸭 💎 React 前端 + Node 后端 + 云开发全栈项目 by 程序员鱼皮

01Result

liyupi/mianshiya ↗

liyupi/mianshiya AI coding statistics: 0%

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

Too little recent activity to publish. Only 3 commits landed in this window, so the percentage is noisy. Repositories below 100 are excluded from the index for this reason.

No signed agent commits found

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

agent commits

other considered commits

—

agent contributors

—

largest contributor

02Drivers

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.

03Evidence

Inspect the matches

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

No matched commit samples are available for this observation.

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

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

Continue exploring

TypeScript AI coding statisticsCompare evidence across TypeScript repositories →GitHub AI commit analyzerInspect another repository with the same evidence model →

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 liyupi/mianshiya

Scan another repository

Try