security-ownership-map

Mapping git history to identify security ownership involves analyzing commit data to build a bipartite graph of contributors and files. This process calculates bus factor metrics and flags sensitive code hotspots where maintenance knowledge is concentrated in too few individuals.

A bipartite graph for code ownership assessment maps contributors to files based on git history. It visually represents who touches what, allowing you to perform reality checks on CODEOWNERS files and identify orphaned security-critical files.

Yes, analyzing sensitive code hotspots requires Python 3 and the networkx library. These dependencies are necessary to construct the ownership graph, perform community detection, and execute ownership clustering algorithms.

To generate a security risk report for orphaned files, run the security ownership analysis script on your repository. It automatically flags sensitive hotspots like auth and crypto code with low bus factors and identifies stale code.

Yes, you can export the git ownership graph for visualization in Neo4j. The analysis generates graph artifacts from the repository history that are compatible with visualization tools like Neo4j to explore contributor and file relationships.

The best way to validate CODEOWNERS files against actual activity is comparing them against a bipartite ownership graph. This graph is built from actual git commit history to verify that listed owners are actively maintaining the code.