security-ownership-map

To calculate bus factor from git history, this skill processes commit data to build a bipartite ownership graph of people-to-files, quantifying sensitive-code ownership and highlighting risk hotspots. It outputs CSV and JSON artifacts for downstream analysis.

Detecting CODEOWNERS drift involves analyzing commit history to map actual file ownership and comparing these relationships against your CODEOWNERS file. This skill computes ownership metrics to surface discrepancies and sensitive-touches in security-sensitive projects.

Yes, you can export git commit ownership graphs to Neo4j or Gephi. This skill generates graph-friendly CSV and JSON artifacts from commit history, allowing you to import the security ownership topology directly into visualization platforms.

Yes, you need Python 3 and the networkx library to analyze code ownership. This skill relies on networkx to process git commits, build the bipartite ownership graph, and compute the security metrics required for your analysis.

A bipartite ownership graph maps relationships between people and files based on commit history. You need it for risk analysis when evaluating large monorepos or security-sensitive projects to identify sensitive-code ownership concentration and bus factor risks.