security-ownership-map

Analyze git repositories to map security ownership and export CSV/JSON.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ThePhoenixAgency/Phoenix-Agents-Marketplace --skill security-ownership-map-thephoenixagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/ThePhoenixAgency/Phoenix-Agents-Marketplace/tree/main/plugins/dev-pipeline/skills/security-ownership-map
Command: npx skills add https://github.com/ThePhoenixAgency/Phoenix-Agents-Marketplace --skill security-ownership-map-thephoenixagency

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 in code by mapping who owns which files, calculating the bus factor (how many people are critical for a file's maintenance), and highlighting sensitive code ownership.

Core Features & Use Cases

  • Ownership Topology: Builds a graph of people and files from git history.
  • Bus Factor & Sensitivity: Computes risk metrics for sensitive code areas.
  • Graph Export: Generates CSV/JSON for visualization in tools like Neo4j or Gephi.
  • Use Case: Detect if critical security files (e.g., in crypto/ or auth/) are maintained by only one person, indicating a high bus factor risk.

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 sensitive code areas using git history?

You can calculate the bus factor for sensitive code by analyzing git history to build an ownership topology, which computes how many maintainers are critical for specific files and highlights single-point maintenance risks.

What is a security ownership topology and when do I need it for risk assessment?

A security ownership topology is a graph mapping people to files based on git history. You need it when identifying orphaned sensitive code or verifying if critical security directories rely on a single maintainer.

How do I export git code ownership data for visualization in Neo4j or Gephi?

You can export git code ownership data by running an analysis script that generates CSV and JSON formats, allowing you to import the ownership topology and risk metrics directly into graph databases like Neo4j or visualization tools like Gephi.

Can I check if my CODEOWNERS file matches the actual git history of security maintainers?

Yes, you can perform a CODEOWNERS reality check by comparing your declared CODEOWNERS file against the actual ownership topology extracted from git commit history to find discrepancies in sensitive code areas.

Does this security ownership analysis require any specific Python dependencies?

Yes, the security ownership analysis requires the networkx Python library to construct the ownership topology graph and compute the bus factor and sensitive code risk metrics from your repository data.

What is the best way to detect orphaned sensitive code in a git repository?

The best way to detect orphaned sensitive code is to map file ownership from git history and compute bus factor metrics to identify critical security files with insufficient or single-person maintenance coverage.