skills.rest
syl2042
syl2042COMMUNITY
Explore all skills by this author →
GitHub

security-ownership-map

Builds security ownership maps from git history and exports CSV/JSON graphs.

Updated Feb 5, 2026
Search Tags:#security#ownership#neo4j#git-history#bus-factor#graph-analysis#co-change
One-click install
npx skills add https://github.com/syl2042/codex_skills --skill security-ownership-map-syl2042
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/syl2042/codex_skills/tree/main/security-ownership-map
Command: npx skills add https://github.com/syl2042/codex_skills --skill security-ownership-map-syl2042

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze git history to identify ownership of code assets, surface ownership gaps, and highlight security-related ownership risks such as brittle bus factors and sensitive code hotspots.

Core Features & Use Cases

  • Build a bipartite graph of people and files from git history and compute ownership risk and sensitive-code ownership.
  • Export ready-to-use artifacts (CSV/JSON and graph formats) for Neo4j/Gephi and visualize file co-change clusters.
  • Use cases include security ownership reality checks, orphaned sensitive code detection, CODEOWNERS drift analysis, and risk profiling.

Quick Start

Run the provided script to generate an ownership map 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 map code ownership and identify bus factor risks from git history?▼

You can map code ownership by building a bipartite graph of people and files from git history. This process computes ownership risk and highlights bus factor vulnerabilities by analyzing who contributes to what files across repositories and time windows.

What is sensitive-code ownership analysis and how does it detect orphaned code?▼

Sensitive-code ownership analysis identifies who maintains security-critical file paths using a CSV config of sensitive patterns. It detects orphaned sensitive code by mapping git history to reveal ownership gaps and files lacking active contributors.

Can I export git ownership graphs for Neo4j and visualize file co-change clusters?▼

Yes, you can export ready-to-use CSV and JSON graph artifacts for Neo4j or Gephi. The analysis clusters files by co-change patterns, allowing you to visualize how files are modified together alongside people-to-file ownership mapping.

Do I need networkx to analyze CODEOWNERS drift and git history ownership?▼

Python 3 is required, while networkx is optional and used specifically for computing community clusters in co-change patterns. You also need a CSV config file to specify sensitive-path patterns for targeted ownership analysis.

What is the best way to perform a security ownership reality check across multiple repositories?▼

The best way is to analyze git history across multiple repositories and time windows to build an automated security ownership map. This approach surfaces ownership gaps, brittle bus factors, and sensitive code hotspots for a comprehensive reality check.

Related Skills

Explore More Data & Analytics Skills→
jovermierjovermier
1

git-history-analyzer

Analyze repository commit history to trace code evolution and ownership.

Community
Basic
pingqLINpingqLIN

security-ownership-map

Analyzes git history to map people-to-files ownership and detect security risks in codebases.

Community
Advanced
alanharrryy-wqalanharrryy-wq
2

security-ownership-map

Analyze git history to map file ownership and compute bus-factor metrics.

Community
Advanced
jaypatrickjaypatrick

security-ownership-map

Generate a security-ownership map from Git history, outputting CSV/JSON artifacts.

Community
Advanced