security-ownership-map

Analyzes git history to map file ownership and compute bus factors for security risk.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/P4rzi/PROT-RISK --skill security-ownership-map-p4rzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/P4rzi/PROT-RISK/tree/main/.github/skills/security-ownership-map
Command: npx skills add https://github.com/P4rzi/PROT-RISK --skill security-ownership-map-p4rzi

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 codebases by analyzing git history to understand who owns which files, compute the bus factor (how many people need to leave before a project is at risk), and detect sensitive code ownership issues.

Core Features & Use Cases

  • Ownership Topology: Builds a graph of people and files from git history.
  • Bus Factor Calculation: Computes the bus factor for files and identifies hotspots.
  • Sensitive Code Analysis: Flags orphaned or poorly-owned sensitive code (auth, crypto, secrets).
  • Graph Export: Generates CSV and GraphML outputs for visualization in tools like Neo4j and Gephi.
  • Use Case: A security team wants to understand the ownership risk for all files tagged as 'crypto' or 'auth'. They can use this skill to find files with a low bus factor and no recent security-focused commits, highlighting potential vulnerabilities.

Quick Start

Run the security-ownership-map skill to analyze the current repository for security ownership and bus factor.

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 my git repository?

To calculate the bus factor for a git repository, this Skill processes git history to map people to files and computes risk metrics. It identifies hotspots where code ownership is concentrated among very few contributors.

What is sensitive code ownership analysis in git?

Sensitive code ownership analysis flags orphaned or poorly-owned critical code, such as auth, crypto, and secrets. It uses git history to identify files with low bus factors and no recent security-focused commits.

Can I export git code ownership topology to a graph database?

Yes, you can export git code ownership topology to a graph database. This Skill generates CSV and GraphML outputs suitable for visualization in tools like Neo4j and Gephi.

Does this bus factor analysis work with my existing CODEOWNERS file?

Yes, this bus factor analysis performs a CODEOWNERS reality check. It compares your declared CODEOWNERS file against actual git history to reveal true ownership risk and orphaned sensitive code.

Do I need networkx to map security ownership from git history?

Yes, you need networkx installed to map security ownership from git history. The Skill uses this dependency to build the graph of people and files and compute the ownership topology.

What are the limitations of using git history for risk assessment?

A limitation of using git history for risk assessment is that it relies solely on commit data to determine ownership. It may not reflect undocumented operational knowledge or recent team changes not yet captured in git.