security-ownership-map

To calculate the bus factor using git history, this skill builds a bipartite ownership graph mapping people to files and computes retention metrics to identify security hotspots and ownership risk across your repositories.

CODEOWNERS drift occurs when actual file authors diverge from defined ownership rules. You can detect it by analyzing git history to map real people-to-files ownership and comparing it against your existing CODEOWNERS file structure.

You can find orphaned sensitive code across multiple repositories by applying sensitivity rules to git history analysis, which surfaces unowned or abandoned critical files in a generated security summary report.

Yes, you can export the git co-change graph to Neo4j or Gephi. The skill generates graph artifacts in CSV, JSON, and GraphML formats specifically designed for import into these visualization tools.

Yes, you need networkx installed to perform community detection on file co-change clusters. This Python dependency is required to cluster related files by shared commit movement and identify ownership drift.

The best way to map security ownership without manual tracking is to parse git commit history to automatically generate a bipartite graph of people and files, computing last-touch times and bus-factor metrics.