security-ownership-map

Map security ownership by analyzing Git history to build a people-to-files topology, computing bus factor metrics, and tagging sensitive code hotspots to identify primary maintainers and ownership drift.

Calculate bus factor risk by analyzing Git history to build a co-change graph and detect community ownership distribution, quantifying how many developers hold critical knowledge across sensitive repository paths.

Export Git ownership data to Neo4j by generating CSV and JSON graph artifacts from the repository history, enabling direct import into graph databases for advanced security ownership topology visualization.

Yes, you need networkx for graph features like community detection and co-change analysis, though basic ownership mapping and bus factor calculations can run with standard Python 3 without it.

Customize sensitive path rules by providing a CSV sensitivity config file, which allows you to define specific repository path patterns for targeted ownership drift and security risk assessment.

Yes, you can use Gephi to visualize Git ownership topology by exporting graph artifacts as CSV or JSON files, which support direct import for rendering co-change graphs and community detection networks.