security-ownership-map

Map git ownership and security risk by analyzing git history to build a bipartite graph of people and files, which surfaces bus factor vulnerabilities and sensitive-code hotspots. The tool exports CSV/JSON outputs and graph artifacts for visualization.

A bus factor analysis evaluates codebase risk by mapping people-to-files ownership from git history to identify orphaned-sensitives and hidden owners. It generates a summary that guides governance and prioritizes security ownership improvements.

Yes, you can export git ownership graphs to Neo4j or Gephi. The analysis produces CSV/JSON outputs and graph artifacts designed for import into graph databases, enabling you to visualize people-to-file relationships and security hotspots.

Yes, this git history ownership analysis requires Python 3 and the networkx dependency to run the included scripts. It processes your repository history and applies configurable sensitive-path rules to compute ownership risk.

Cluster related files by enabling the optional co-change analysis feature to generate a co-change graph from your git history. This groups files that frequently change together, helping you understand code coupling and community maintenance patterns.

Using git history to identify hidden owners relies strictly on commit metadata, meaning it may miss contributors who commit under alternate identities or external dependencies. It requires configurable sensitive-path rules to accurately target specific security hotspots.