skills.rest
heyzude
heyzudeCOMMUNITY
Explore all skills by this author →
GitHub

security-ownership-map

Analyze git repositories to generate security ownership topology and bus factor data.

4|Updated Feb 13, 2026
Search Tags:#git#security#maintainability#risk analysis#bus factor#code ownership
One-click install
npx skills add https://github.com/heyzude/skills_for_codex --skill security-ownership-map-heyzude
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/heyzude/skills_for_codex/tree/main/skills_by_openai/security-ownership-map
Command: npx skills add https://github.com/heyzude/skills_for_codex --skill security-ownership-map-heyzude

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 mapping who owns which files, calculating the "bus factor" (how many people are critical for a file's maintenance), and highlighting sensitive code that might be under-maintained or owned by too few individuals.

Core Features & Use Cases

  • Ownership Mapping: Creates a graph of people and files based on git history.
  • Bus Factor Calculation: Determines the minimum number of people needed to maintain a file or module.
  • Sensitive Code Analysis: Identifies files tagged as sensitive (e.g., auth, crypto) and analyzes their ownership and bus factor.
  • Use Case: A security team can use this to check if critical authentication modules have a low bus factor, indicating a high risk if those few maintainers leave.

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 in a git repository?▼

You can identify orphaned sensitive code by analyzing git history to map file ownership and compute the bus factor. This process flags security-critical modules that are maintained by too few individuals or lack active ownership.

How does git history mapping identify security maintainer risks?▼

Git history mapping identifies security maintainer risks by generating an ownership topology that links people to files. It computes the bus factor to highlight sensitive code maintained by too few individuals, indicating potential security vulnerabilities.

Can I export code ownership topology data for graph databases?▼

Yes, you can export code ownership topology data for graph databases. The Skill outputs the generated git history analysis and bus factor metrics in CSV and JSON formats suitable for import into graph databases and visualization tools.

Does this security ownership analysis require a CODEOWNERS file to work?▼

You can analyze sensitive code ownership by extracting git commit history to map maintainers to files. This computes the bus factor for security-critical modules, identifying risks where too few individuals maintain sensitive code.

Related Skills

Explore More Software Engineering Skills→
joonlabjoonlab
8

git-manager

Split project files between Git repositories and Hugging Face datasets.

Community
Advanced
MatheusrlrMatheusrlr
1

security-ownership-map

Analyze git repositories to construct security ownership topology and export CSV and JSON data.

Community
Advanced
ChatAndBuildChatAndBuild
1

security-ownership-map

Analyze git repositories to compute bus factor and sensitive-code ownership.

Official
Advanced
dajneem23dajneem23

security-ownership-map

Analyze git history to map security ownership and compute bus factor.

Community
Advanced