security-ownership-map

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

2|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Sacred-G/oh-my-claw --skill security-ownership-map-sacred-g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/Sacred-G/oh-my-claw/tree/main/secure-openclaw/skills-main/skills/.curated/security-ownership-map
Command: npx skills add https://github.com/Sacred-G/oh-my-claw --skill security-ownership-map-sacred-g

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze git history to map security ownership between people and files, identify ownership risk, and compute bus factor, exporting CSV/JSON artifacts for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.

Core Features & Use Cases

  • Build a bipartite graph of people and files from git history, compute ownership risk, and export artifacts for Neo4j/Gephi.
  • Create a file co-change graph (Jaccard similarity on shared commits) to cluster files by movement patterns.
  • Persist outputs (people.csv, files.csv, edges.csv, cochange_edges.csv, summary.json) and offer query helpers for bounded data slices.

Quick Start

Run the ownership map generator from the project root to produce the analysis and artifacts 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 security ownership and find orphaned sensitive code in my repository?

You can identify orphaned sensitive code by analyzing git history to map security ownership between people and files. This Skill builds a bipartite graph, computes ownership risk, and exports CSV artifacts for graph databases like Neo4j or Gephi.

How do I calculate bus factor exposure for security-critical code paths?

Calculating bus factor exposure involves analyzing git history to map file ownership and identify sensitive hotspots with limited maintainers. This Skill computes ownership risk and exports a summary.json file detailing bus-factor exposure across modules.

How does file co-change graph clustering work for security ownership risk analysis?

File co-change graph clustering works by computing Jaccard similarity on shared commits to cluster files by movement patterns. This Skill generates cochange_edges.csv to reveal security maintainers and ownership clusters across sensitive modules.

Do I need networkx and Python 3 to analyze git history for CODEOWNERS drift?

Yes, you need Python 3 and the networkx library to analyze git history for CODEOWNERS drift. This Skill relies on networkx to construct the ownership graph and export CSV artifacts for visualizing security risk profiles.

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

Yes, you can export git history ownership graphs to Neo4j or Gephi. This Skill analyzes git history to map security ownership and generates CSV files like edges.csv and people.csv specifically formatted for graph database import and visualization.