security-ownership-map

Git history ownership mapping analyzes commits to build a bipartite people-to-files graph, computing bus factor risk and identifying sensitive-code hotspots. It outputs CSV and JSON artifacts containing ownership and co-change graph data.

Bus factor analysis in security ownership quantifies repository risk by calculating how many developers actively maintain sensitive code areas. It applies git history mapping to identify orphaned code or security-critical paths lacking sufficient developer coverage.

Yes, detecting CODEOWNERS drift and orphaned sensitive code is possible by analyzing git history against configured sensitive-path rules. This identifies files where ownership records have diverged from actual commit activity, flagging remediation targets for security audits.

Yes, Python 3 and the networkx library are required dependencies to generate ownership and co-change graphs. These components construct the bipartite graphs and perform optional community detection for risk clustering across the analyzed codebase.

Exporting git history ownership graphs for Neo4j or Gephi requires running the analysis to produce CSV and JSON artifacts. These standard formats contain graph nodes and edges, enabling direct import into graph databases and network visualization platforms.

Sensitive-path rules for security risk clustering should be used when isolating high-risk directories or files within large codebases. They focus the ownership and bus factor analysis specifically on security-critical code movement patterns and potential orphaned areas.