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.

Agent-less vulnerability scanner for Linux, FreeBSD, Container, WordPress, Programming language libraries, Network devices

01Result

future-architect/vuls ↗

future-architect/vuls AI coding statistics: 51.1%

of 94 commits in February–September 15, 2026 were committed by an AI agent — a floor, not an estimate
Too little recent activity to publish. Only 94 commits landed in this window, so the percentage is noisy. Repositories below 100 are excluded from the index for this reason.
51.1% agent · top contributor 41.7%6 contributors
team

A small group is using agents. Adoption has spread beyond one person but is not project-wide.

48
agent commits
46
other considered commits
6
agent contributors
41.7%
largest contributor

02Drivers

What shapes this result

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

Assisted or autonomous

45assisted
3autonomous

Assisted — a developer’s identity authored the commit and the agent added itself as co-author. Autonomous — a bot identity authored the commit without a human identity attached.

Agent share by month

Agent-attributed commit share by month
MonthAgent shareConsidered commits
2026-020%17
2026-0326.3%19
2026-0446.2%13
2026-0563.6%11
2026-0690%10
2026-07100%13
2026-0877.8%9
2026-0950%2

Peak month: 100%. Bars are scaled to that peak, not to 100%.

Which agents

AgentVendorCommitsShare
Claude CodeAnthropic4042.6%
GitHub CopilotGitHub1010.6%

03Evidence

Inspect the matches

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

Matched commit samples

  • 5dd453fb on GitHubperf(detector/vuls2): fold vuls2 detections from the streaming Detect (#26Claude Code
  • 6499d0e9 on GitHubfix(detector/vuls2): break CVSS merge score ties deterministically (#2649)Claude Code
  • e901c00f on GitHubfix(models): map trivy-db julia, seal, and redhat-csaf-vex sources (#2646)Claude Code
  • 6ef6ba40 on GitHubfeat!(detector): detect windows with vuls2 (#2499)GitHub Copilot
  • 18abe611 on GitHubtest(scanner): source lockfiles from vulsio/integration (#2531)GitHub Copilot
  • 4c71b0ac on GitHubfeat!(detector): replace go-exploitdb with vuls2 (#2517)GitHub Copilot

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 window132
Merge commits removed−0
CI / dependency bots removed−38
Considered94

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

Continue exploring

Claude Code commitsBrowse repositories with detected Claude Code signatures →GitHub Copilot commitsBrowse repositories with detected GitHub Copilot signatures →Go AI coding statisticsCompare evidence across Go 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 future-architect/vuls

Scan another repository

Try