security-ownership-map

Calculating the bus factor using git history requires analyzing commit patterns to find the minimum number of maintainers needed for specific files or modules. This skill processes your repository to compute that exact risk metric.

A security ownership topology maps relationships between developers and files extracted from git history to identify security risks. It highlights sensitive code areas, such as authentication or crypto modules, and detects orphaned code lacking active maintainers.

Checking if your CODEOWNERS file matches reality requires performing a reality check by comparing documented owners against actual commit data. This skill analyzes git history to reveal discrepancies between assigned and active maintainers.

Exporting git code ownership data for visualization in Neo4j or Gephi requires generating structured graph outputs. This skill exports the analyzed security topology and ownership data in CSV and JSON formats specifically designed for graph databases.

Running this git security analysis requires the networkx dependency to construct the graph topology of people and files. You execute the analysis script directly from your repository root to process the current directory's commit history.

Identifying orphaned sensitive code in your repository requires analyzing git history to map ownership of authentication, crypto, and secrets-related files. This skill detects sensitive modules lacking sufficient active maintainers or having a low bus factor.