Coding Agent Radar

Detection strategy

A repository is counted as using a coding agent when it contains one or more agent-specific config files. No file contents are read and no LLM is involved.

Data collection

For each signal file the GitHub Code Search API is queried (up to 1000 results per signal). Results are returned in best-match order. Each matched repository is enriched with full metadata via a separate API call, cached to avoid redundant fetches across signals.

A repository is counted once per agent regardless of how many of its signal files match. The scanner runs weekly and preserves original discovery dates across re-runs.

Limitations

• Repos using an agent without committing a config file are not counted.
• Only public GitHub repositories are covered.
• The timeline reflects scan date, not the original commit date.
• All GitHub Code Search API limitations apply — including the 1000 result cap per query, index delays, and potential gaps in coverage for recently pushed or low-activity repositories.
• GitHub forces results to be sorted by relevance ("best match") — sorting by stars is not supported by the API. High-starred repos are therefore not guaranteed to appear and may be missing from the data.