Security Ownership Map
Analyzes git history to map security ownership topology, calculate bus factors for sensitive code, and identify high-risk maintenance clusters.
This skill provides deep insights into the human-to-code relationship within a git repository from a security perspective. By building bipartite and co-change graphs from commit history, it identifies orphaned sensitive code, calculates the 'bus factor' for critical components like authentication and cryptography, and detects hidden ownership clusters. It is particularly useful for security audits, verifying CODEOWNERS accuracy, and visualizing repository health through graph databases like Neo4j or visualization tools like Gephi, helping teams mitigate risks associated with knowledge silos and unmaintained security-critical files.