Codebase

See which parts of your codebase change the most

About

The Codebase view shows what's happening in your codebase: which parts of it change the most and who's changing them.

You can find it at Metrics → Code metrics → Codebase. It shows a tree of repositories, folders, and files, aggregated from the files changed in merged pull requests.

The metrics are based on the filenames modified in your pull requests. Swarmia doesn't read your source code. Read more about data access.

File changes

Each row in the table is a repository, folder, or file. Expand rows to drill down the tree. For each row, you can see:

• PRs: the number of pull requests that changed files in this location. Click the count to see the pull requests.

• Authors: the number of people who authored those pull requests. Click the count to see who they are.

• Changes: the lines added and deleted.

• % changes: this location's share of all line changes in the current view.

Sort by any of these columns to surface the most active parts of the codebase. By default, the view covers your whole organization; narrow it down with:

• Teams: focus on the pull requests of one or more teams.

• Timeframe: pick the date range in the top-right corner.

• Pull request filters: for example, filter by repository or by AI attribution tag to see which files AI tools have been changing.

Some questions the view can answer:

• Which files have the most pull request activity this quarter? Would they benefit from refactoring, better test coverage or clearer ownership?

• Which parts of the codebase has our team worked on recently?

• Where have AI coding assistants made changes, and how much?

• Who has contributed to this legacy module lately?

• Are there knowledge silos, such as critical areas with only one recent contributor?

Where does the data come from?

The view is based on merged pull requests and the file paths, additions, and deletions reported by GitHub or GitLab. Pull requests excluded by your pull request settings don't appear here. You can change the status filter to include open or closed pull requests, too.

A few limits to be aware of:

• One view can cover up to 100,000 pull requests. If your filters match more, Swarmia shows a warning and asks you to narrow them down for complete results.

• For exceptionally large pull requests, Swarmia stores only part of the file list, so some files from those pull requests may be missing.

• Author counts are based on the pull request author, not individual commit authors.