security-ownership-map

Build a bipartite ownership graph from git history and compute bus-factor risk.

Updated May 25, 2026
One-click install
npx skills add https://github.com/pawan0631/AI_OpenAISkill --skill security-ownership-map-pawan0631
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/pawan0631/AI_OpenAISkill/tree/main/skills/.curated/security-ownership-map
Command: npx skills add https://github.com/pawan0631/AI_OpenAISkill --skill security-ownership-map-pawan0631

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires networkx, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Analyzing a repository's git history to identify security ownership, potential bus-factor risks, and ownership drift across code files, enabling proactive risk visibility and governance.

Core Features & Use Cases

  • Build a bipartite ownership graph of people and files from commit history to surface ownership patterns and hotspots.
  • Generate a co-change graph to cluster files by co-edits, supporting risk analysis and change impact assessment.
  • Export graph artifacts (CSV/JSON) for Neo4j/Gephi and provide summaries of orphaned_sensitive_code and hidden_owners for governance reviews.
  • Use cases include security-aware maintenance planning, CODEOWNERS audits, and risk visualization for large codebases.

Quick Start

Run the ownership map against a repository to output the graphs and summary for downstream visualization and queries.

Frequently Asked Questions about security-ownership-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze git history to find sensitive code ownership and bus factor risks?

Analyzing git history for sensitive code ownership involves building a bipartite graph of people and files from commit history to compute bus factor and identify ownership hotspots. This surfaces orphaned sensitive code and hidden owners for governance reviews.

What is a co-change graph and when do I need it for repository risk analysis?

A co-change graph clusters files by co-edits from git history to support risk analysis and change impact assessment. You need it when identifying ownership drift or visualizing risk hotspots in large codebases to understand how file changes correlate.

Can I export ownership graph data to Neo4j or Gephi for visualization?

Yes, you can export ownership graph data to Neo4j or Gephi by generating CSV and JSON outputs from the git history analysis. These graph artifacts are structured for direct import into graph databases and visualization tools.

Does the ownership map workflow support CODEOWNERS audits and orphaned code analysis?

Yes, the ownership map workflow supports CODEOWNERS audits and orphaned code analysis by summarizing hidden owners and orphaned sensitive code from commit history. It provides configurable Python scripts to query ownership data for governance reviews.

Do I need networkx to run the git history ownership map scripts?

Yes, you need networkx to run the git history ownership map scripts because it provides the graph data structures required for building the bipartite ownership graph and performing community detection.