security-ownership-map

To identify orphaned sensitive code in git history, this Skill analyzes commit timestamps and ownership data to find security-critical files, such as those handling secrets, that have not been modified or actively maintained for over a year.

The best way to map git history to a security ownership topology is by analyzing commit co-occurrence to cluster files and construct a graph linking developers to sensitive code. This reveals ownership drift and community structures within the codebase.

Yes, you need Python 3 and the networkx library to run this git code ownership analysis. Networkx is specifically required to perform the community detection and graph analysis needed to compute the bus factor and ownership topology.

Yes, you can export git ownership graphs to Neo4j and Gephi because this Skill generates CSV and JSON outputs containing the security ownership topology and co-change clusters. These standard formats are directly importable into graph databases and visualization platforms.

Co-change graphing helps find sensitive code ownership drift by clustering files based on their co-occurrence in commits, revealing how code evolution patterns shift over time. This highlights when sensitive modules move away from their original maintainers.