security-ownership-map

Analyze git repositories to map security ownership and calculate bus factors.

24.7k|1.7k|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/openai/skills --skill security-ownership-map-openai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/openai/skills/tree/main/skills/.curated/security-ownership-map
Command: npx skills add https://github.com/openai/skills --skill security-ownership-map-openai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify security risks by mapping code ownership, calculating the bus factor (how many people are critical to a project), and analyzing the ownership of sensitive code.

Core Features & Use Cases

  • Ownership Topology: Creates a graph of people and files based on git history.
  • Risk Analysis: Computes bus factor and sensitive code ownership.
  • Data Export: Outputs CSV/JSON for visualization tools like Neo4j and Gephi.
  • Use Case: Identify critical files with a low bus factor that are also tagged as sensitive (e.g., crypto or auth code), highlighting potential single points of failure or security vulnerabilities.

Quick Start

Run the security ownership map script on the current repository to analyze git history and output ownership data.

Frequently Asked Questions about security-ownership-map

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

FAQPage Schema
How do I calculate the bus factor for a git repository?

To calculate the bus factor for a git repository, you can analyze the git history to construct an ownership topology. This process identifies critical files and computes how many people are essential to maintaining sensitive code areas.

What is sensitive code ownership analysis?

Sensitive code ownership analysis identifies who maintains critical components like crypto or auth code by mapping git history. It highlights potential single points of failure and security vulnerabilities when ownership is concentrated.

How do I export git code ownership data for graph visualization?

You can export git code ownership data for graph visualization by analyzing the repository history and outputting the results in CSV or JSON formats. These files are structured specifically for import into graph databases and tools like Neo4j and Gephi.

Does the ownership topology analysis require external dependencies?

The ownership topology analysis requires the networkx dependency to construct graphs of people and files. You need a local git repository with sufficient commit history to accurately map the ownership structure and calculate risk metrics.

Can I identify orphaned sensitive code using git history?

Yes, you can identify orphaned sensitive code by analyzing git history to map ownership clusters. The analysis triggers specifically for security-oriented ownership, flagging sensitive files that lack active maintainers or have a critically low bus factor.