skills.rest
cloudofgeorge
cloudofgeorgeCOMMUNITY
Explore all skills by this author →
Website𝕏@cloudofgeorgeGitHub

security-ownership-map

Analyze git histories to map people-to-files ownership and surface security risks.

Updated May 11, 2026
Search Tags:#security#CODEOWNERS#graph-database#git-history#bus-factor#ownership-map
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --skill security-ownership-map-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/security-ownership-map
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill security-ownership-map-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze git histories to map people-to-files ownership and surface security hotspots.

Core Features & Use Cases

  • Build a provenance-backed ownership graph from commit history.
  • Identify orphaned or high-risk code by sensitivity tags and bus factors.
  • Generate CSV/JSON artifacts (people.csv, files.csv, edges.csv, summary.json) for graph databases and visualization.

Quick Start

Run the ownership map on your repository to produce the standard artifacts and summaries.

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 find security risks in git history?▼

To map git ownership and security risks, analyze commit histories to build a provenance-backed ownership graph that surfaces orphaned sensitive code, CODEOWNERS drift, and bus-factor hotspots across your repository.

What is a bus-factor hotspot and how do I identify it in my repository?▼

A bus-factor hotspot is code maintained by very few contributors, creating project risk. Identify these hotspots by analyzing your git history to map people-to-files ownership and surface files with dangerously low contributor counts.

How do I detect CODEOWNERS drift and orphaned sensitive code in my git repository?▼

Detect CODEOWNERS drift and orphaned sensitive code by applying a configurable Python workflow to your git history, mapping people-to-files ownership and flagging high-risk code based on sensitivity tags and bus factors.

Can I export my git ownership graph to Neo4j or Gephi for visualization?▼

Yes, you can export your git ownership graph to Neo4j or Gephi. The workflow generates standard CSV and JSON artifacts like people.csv, files.csv, and edges.csv that provide optional graph representations for database import.

What file outputs do I get when analyzing git ownership and security hotspots?▼

Analyzing git ownership produces CSV and JSON artifacts including people.csv, files.csv, edges.csv, cochange_edges.csv, and a summary.json file detailing ownership provenance, security risks, and bus-factor metrics.

Does this git ownership mapping workflow require any external dependencies?▼

No, this git ownership mapping workflow requires no external dependencies to run. It uses a configurable Python workflow with included scripts and references to analyze your repository history and output ownership artifacts.

Related Skills

Explore More Software Engineering Skills→
jkitchinjkitchin
34

python-regression-statistics

Guide regression analysis and outlier detection in Python using statsmodels, scikit-learn, scipy, and PyOD.

Community
Advanced
JaimeJunrJaimeJunr
2

security-ownership-map

Generate a people-to-files ownership topology with risk hotspots from git history.

Community
Advanced
bl1nk-botbl1nk-bot
3

security-ownership-map

Build a security ownership map from git history to identify risk hotspots.

Official
Advanced
dajneem23dajneem23

security-ownership-map

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

Community
Advanced