security-ownership-map

Maps people to Git files to build security ownership topology.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Builds a security ownership topology by mapping people to files from git history, computing bus factor, and identifying sensitive code ownership, enabling visibility into ownership gaps and risk clusters across a codebase.

Core Features & Use Cases

  • Builds a bipartite ownership graph from commit history, exporting CSV/JSON graphs and a summary for auditing and visualization.
  • Identifies hotspots, ownership drift relative to CODEOWNERS, and security-relevant file clusters to guide remediation and governance.
  • Produces per-community maintainers and threat-aware summaries to support security reviews and risk assessments.

Quick Start

Run the ownership map to generate graphs and a security ownership summary for your repository.

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 codebase from git history?

To calculate the bus factor from git history, this Skill builds a bipartite ownership graph mapping developers to files, then analyzes ownership risk to identify sensitive code hotspots and ownership gaps. It exports CSV/JSON graphs and an auditing summary.

What is security ownership drift and how is it detected relative to CODEOWNERS?

Security ownership drift occurs when actual file ownership from git history diverges from defined CODEOWNERS rules. This Skill detects drift by mapping commit authors to files, comparing the resulting topology against CODEOWNERS, and highlighting ownership gaps.

How do I generate an ownership graph from git history for security audits?

You generate an ownership graph for security audits by running scripts that map people to files from commit history. The process exports CSV and JSON graphs alongside a threat-aware summary to support security reviews and risk assessments.

Does this ownership mapping tool require networkx to analyze code communities?

Yes, this ownership mapping tool requires networkx as a dependency to perform co-change clustering and extract community-based insights. It uses the library to build the graph and compute per-community maintainers for the security summary.

Can I configure sensitivity rules for identifying security hotspots in my repository?

Yes, you can configure sensitivity rules to identify security hotspots in your repository. The analysis uses these configurable rules to flag security-relevant file clusters, guiding remediation and governance efforts based on your specific codebase context.