security-ownership-map

Analyze git repository ownership topology and export CSV/JSON data.

Updated May 4, 2026
One-click install
npx skills add https://github.com/luokai25/luo-ai-skills-market --skill security-ownership-map-luokai25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/luokai25/luo-ai-skills-market/tree/main/06-security-and-auth%20%28by%20Luo%20Kai%29/07-compliance-auditing/openai-security-ownership-map
Command: npx skills add https://github.com/luokai25/luo-ai-skills-market --skill security-ownership-map-luokai25

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you analyze security ownership in git repositories, compute bus factor and sensitive-code ownership, and export data for graph databases and visualization.

Core Features & Use Cases

  • Security Ownership Topology: Maps the relationships between developers and files for security risk assessment.
  • Bus Factor Calculation: Determines the number of developers who have touched a particular piece of code.
  • Sensitive Code Ownership: Identifies ownership of sensitive files and assesses risk.
  • Export Data: Exports the ownership data in CSV/JSON format for graph databases and visualization tools.
  • Use Case: You have a complex repository with many contributors. This Skill helps you understand who owns which parts of the codebase and identify potential risks.

Quick Start

Run the 'security-ownership-map' skill on your repository to analyze security ownership.

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, this Skill analyzes commit history to determine how many developers have touched specific code. It outputs the resulting ownership topology and risk metrics in CSV or JSON format.

What is sensitive code ownership analysis in git?

Sensitive code ownership analysis in git identifies which developers own critical files to assess security risk. It maps developer-file relationships, highlighting potential vulnerabilities when sensitive code is concentrated among too few contributors.

Do I need Python and networkx to analyze git ownership topology?

Yes, you need Python 3 and the networkx dependency installed to analyze git ownership topology. These prerequisites are required to compute the security relationships and map the topology within the repository.

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

You export git ownership data for graph database visualization by running the analysis script to map developer and file relationships. The tool exports the computed topology and risk metrics directly into CSV or JSON formats.

Can I assess security risk by mapping developer contributions to files?

Yes, you can assess security risk by mapping developer contributions to files. This approach computes the bus factor and identifies sensitive code ownership, revealing structural vulnerabilities in complex codebases with many contributors.