security-ownership-map

Generate ownership maps from git history with CSV/JSON outputs for graph analysis.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/pchemguy/Dummy --skill security-ownership-map-pchemguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/pchemguy/Dummy/tree/main/docs/AgentSkills/openai/skills/skills/.curated/security-ownership-map
Command: npx skills add https://github.com/pchemguy/Dummy --skill security-ownership-map-pchemguy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Traditional security ownership tracing across a codebase is manual and error-prone, making it hard to identify owners, risky hotspots, and bus-factor concerns.

Core Features & Use Cases

  • Build a git-history based ownership map linking people to files and compute ownership risk and sensitive-code hotspots.
  • Export graph artifacts for graph databases (CSV/JSON) and visualize clusters; supports co-change graphs and community detection when networkx is available.
  • Use cases include risk auditing, CODEOWNERS reality checks, and identifying orphaned or overburdened owners in large repos.

Quick Start

Run the ownership map on the repository to generate the outputs 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 git history to calculate the bus factor for my repository?

To map git history and calculate the bus factor, this script parses commit logs or a commits.jsonl file to compute recency-weighted contributions. It identifies overburdened or orphaned owners and exports a structured summary.json detailing repository risk.

How do I identify sensitive code hotspots and ownership drift in a codebase?

Identifying sensitive code hotspots and ownership drift involves applying default sensitive rules to parsed git history. The process computes recency-weighted contributions to link people to files, flagging risky areas and outputting structured CSV artifacts for auditing.

Can I export a co-change graph and run community detection using networkx?

Yes, you can export a co-change graph and run community detection using networkx. The script generates cochange_edges.csv and applies community detection algorithms when the networkx dependency is available, supporting visualization in tools like Gephi.

What is the best way to check if my CODEOWNERS file matches actual git history?

The best way to check if a CODEOWNERS file matches reality is to parse git history and compute actual file ownership based on recency-weighted contributions. This generates a files.csv artifact to audit ownership drift against declared owners.

Does this ownership mapping workflow support direct export to Neo4j?

Yes, this ownership mapping workflow supports direct export to Neo4j. It generates structured graph artifacts including people.csv, files.csv, and edges.csv, which are formatted specifically for ingestion into graph databases and dashboards.

Do I need a commits.jsonl file to analyze repository risk hotspots?

You do not strictly need a commits.jsonl file to analyze repository risk hotspots. The script-driven workflow can parse standard git history directly from the repository, or accept a pre-generated commits.jsonl file as input.