security-ownership-map

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

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill security-ownership-map-shalevamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/shalevamin/The-_Ultimate_agents/tree/main/.claude/skills/security-ownership-map
Command: npx skills add https://github.com/shalevamin/The-_Ultimate_agents --skill security-ownership-map-shalevamin

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 identify security risks in code by mapping who owns which files, calculating the bus factor (how many people are critical to a file's maintenance), and highlighting sensitive code that might be neglected or have unclear ownership.

Core Features & Use Cases

  • Ownership Mapping: Creates a graph of people and files based on git history.
  • Bus Factor Calculation: Determines how many individuals are essential for maintaining specific files or code areas.
  • Sensitive Code Analysis: Identifies files tagged as sensitive (e.g., auth, crypto) and analyzes their ownership and staleness.
  • Graph Export: Outputs data in CSV and GraphML formats for visualization tools like Neo4j and Gephi.
  • 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 maintainers leave.

Quick Start

Run the security-ownership-map skill to analyze the current repository's git history and output ownership data to the 'ownership-map-out' directory.

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

To map code ownership and security risks, this Skill analyzes git history to construct a topology of people and files, calculating the bus factor to identify sensitive code with low maintainer counts.

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

Identifying orphaned sensitive code involves analyzing git history to map file ownership and check CODEOWNERS reality against risk, highlighting sensitive files that might be neglected or have unclear ownership.

Can I export git ownership data to Neo4j or Gephi for visualization?

Yes, you can export git ownership data to Neo4j and Gephi for visualization by outputting the analysis results in CSV and GraphML formats to the 'ownership-map-out' directory.

Does security ownership analysis work without a CODEOWNERS file?

Yes, security ownership analysis works without a CODEOWNERS file by deriving the ownership topology directly from git commit history, creating a graph of people and files to check reality against risk.

How do I assess security maintainers for critical authentication modules?

You assess security maintainers by analyzing git history to compute the bus factor for critical authentication modules, indicating high risk if those essential maintainers leave the project.