security-ownership-map

To analyze the bus factor for sensitive code, you can run the `run_ownership_map.py` script against your repository. It parses git history to compute the bus factor and identify single points of failure in critical security components.

Security ownership topology maps people and files from git history to identify ownership clusters and sensitive code ownership. It helps visualize potential security risks by highlighting who controls critical components in the codebase.

You can export git ownership analysis results in CSV or JSON format using the `run_ownership_map.py` script. This outputs ownership maps, sensitivity scores, and community detection data for graph databases and visualization tools like Neo4j and Gephi.

Yes, you need both git and networkx installed to map repository ownership and sensitivity scores. These dependencies are required to parse git history and perform community detection for the analysis.

Yes, you can use this approach to identify single points of failure during a security audit. It computes the bus factor for sensitive code, identifies ownership clusters, and outputs sensitivity scores to assess risk in large codebases.

The best way to run a bus factor analysis on a local codebase is to execute `python scripts/run_ownership_map.py --repo . --out ownership-map-out`, which generates ownership maps and sensitivity scores from your git history.