security-ownership-map

Calculate bus factor from git history by analyzing commit logs to map people-to-files ownership and quantify risk. The tool processes repository commits to identify how many developers hold critical knowledge before a project becomes vulnerable to personnel loss.

Detect CODEOWNERS drift and orphaned sensitive code by cross-referencing declared ownership rules against actual git commit patterns. The tool performs quick checks across repositories to reveal sensitive files lacking active maintainers or mismatched assignments.

Yes, you can export git ownership graphs to CSV and JSON for visualization and graph databases. The tool builds bipartite people-to-files ownership graphs and file co-change clusters, outputting structured artifacts for downstream analysis.

You need Python and access to git history to map code ownership and security hotspots, while networkx is optional for community detection. The tool requires these dependencies to compute ownership graphs and identify sensitive code clusters.

The best way to quantify sensitive code ownership risk for auditing is to analyze git history and compute bus factors for high-risk files. This approach reveals stale code, identifies sensitive hotspots, and generates structured CSV artifacts for governance.