security-ownership-map

To identify orphaned sensitive code and ownership clusters from git history, analyze commit data to build a bipartite person-file ownership map. This process highlights ownership risk by showing exactly who owns specific sensitive files.

CODEOWNERS drift is the discrepancy between actual file ownership derived from commit history and the rules defined in your CODEOWNERS file. You can calculate this drift by mapping commit authors to files and comparing the resulting topology against the expected owners.

You compute the bus factor for sensitive files by analyzing git history to map contributors to those specific paths. A low number of unique contributors to sensitive code hotspots indicates a high-risk bus factor.

Yes, you can use networkx to generate a security ownership topology by creating a bipartite graph of people and files from commit history. This approach requires Python and networkx to process the repository data and compute ownership metrics.

You export git ownership analysis data by generating CSV and JSON artifacts from the computed person-file ownership graph. These artifacts contain the nodes and edges needed to import the security ownership topology into graph databases and visualization platforms.

Yes, you need a sensitive-path CSV to target the ownership analysis specifically at critical files. Accepting this CSV input allows the analysis to focus on identifying orphaned sensitive code and ownership clusters within those defined paths.