- Dataset
- 2026-10-27-catalog-ai-v2
- Ruleset
- b2e8889c66f7
- Scanned
- 2026-10-27
- Window
- February–September 15, 2026
一站式全渠道业务中台系统包括订单管理系统OMS/电商ERP、库存WMS统一管理系统和SAP财务管理系统等,实现快速部署,并帮助企业后续自主进行开发迭代,实现数字化转型,并有多个经典案例。中台系统包括:通用业务中台、强大的技术中台Springcloud/Istio、后续开发方案的设计,技术(K8S,SERVERLESS)及管理人员的培训等。
01Result
FJ-OMS/oms-erp ↗FJ-OMS/oms-erp AI coding statistics: 0%
No signed agent commits found
No agent signatures were found in the last 0 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 | 0 |
| Merge commits removed | −0 |
| CI / dependency bots removed | −0 |
| Considered | 0 |
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 FJ-OMS/oms-erp