security-ownership-map

Analyze git history to build a security ownership topology with bus-factor analysis.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/devkeni/Skills --skill security-ownership-map-devkeni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/devkeni/Skills/tree/main/security/security-ownership-map
Command: npx skills add https://github.com/devkeni/Skills --skill security-ownership-map-devkeni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Build a security ownership map from Git history to identify ownership gaps, bus factor, and hotspots for sensitive code.

Core Features & Use Cases

  • Analyze repository history to attribute touches by contributor, detect stale ownership, and expose risk areas.
  • Generate ownership graphs and summary artifacts for downstream analysis (CSV/JSON/graphml).
  • Use cases include security audits of CODEOWNERS drift, maintainer clustering, and risk visualization for sensitive code.

Quick Start

Run the ownership map pipeline from the repository root to generate the graphs and summary.

Frequently Asked Questions about security-ownership-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map security ownership from Git history to find orphaned sensitive code?

To map security ownership from Git history, you analyze contributor touches to build a people-to-file topology. This exposes orphaned sensitive code by attributing file changes and detecting stale ownership across repositories.

What is CODEOWNERS drift and how do I detect it in my repositories?

CODEOWNERS drift occurs when actual code contributions diverge from defined CODEOWNERS rules. You detect it by analyzing git history to identify stale ownership and risk clusters where active contributors no longer match expected owners.

How do I calculate the bus factor for sensitive code in a repository?

You calculate the bus factor for sensitive code by analyzing git history to count active contributors per file. Configurable sensitivity rules identify critical files, while co-change analysis reveals risk clusters with low contributor diversity.

Can I export ownership graph data to visualize risk clusters in external tools?

Yes, you can export ownership graph data to visualize risk clusters. The pipeline generates exportable graph artifacts in CSV, JSON, and graphml formats for downstream analysis in databases and visualization platforms.

Does this ownership mapping approach require any external dependencies to run?

No external dependencies are required to run this ownership mapping approach. The pipeline operates independently using repository history and configurable sensitivity rules to generate co-change analysis and graph artifacts.

When should I apply co-change analysis during a security audit?

Apply co-change analysis during a security audit when you need to identify risk clusters across repositories. It tracks files frequently modified together to expose maintainer clustering and hidden ownership dependencies in sensitive code.