Code Ownership & Bus Factor

Bus factor risk and code ownership gaps are identified by mining git commit history to build a bipartite graph of people and files, exposing subsystems maintained by only one or two people. It outputs an evidence-based ownership map highlighting single points of failure.

A CODEOWNERS drift check compares your declared ownership rules against recent git commit activity to find mismatches where stated owners do not match actual contributors. It generates a security-oriented ownership map to highlight areas where actual maintenance responsibility has shifted.

Sensitive file ownership review targets areas like auth, crypto, payments, secrets, admin, RBAC, and schema migrations by analyzing git commit history. The ownership map applies sensitivity rules to these paths and exports findings to CSV and GraphML formats.

Co-change clustering groups files that move together in git commits to reveal likely module boundaries and cross-team collaboration zones. It builds an ownership graph from commit history that can be exported as GraphML for downstream analysis of these structural patterns.

Git log access is required to build a security-oriented ownership map because the Skill mines commit history to construct a bipartite graph of people and files. Time-window filtering is also supported to scope your analysis to a specific period of activity.

The best way to export an ownership graph for downstream security analysis is to generate CSV and GraphML outputs directly from the git history mining process. These formats preserve the bipartite graph of people and files along with bus factor and sensitive file findings.