skills.rest
Estom
EstomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

security-ownership-map

Builds a people-to-file security ownership topology from git history and exports CSV/JSON artifacts.

Updated Mar 17, 2026
Search Tags:#git#security#neo4j#networkx#bus-factor#ownership-map#cochange
One-click install
npx skills add https://github.com/Estom/aiflex --skill security-ownership-map-estom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/Estom/aiflex/tree/main/skills-repo/openai-skills/security-ownership-map
Command: npx skills add https://github.com/Estom/aiflex --skill security-ownership-map-estom

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill analyzes git history to produce a people-to-file ownership topology that surfaces maintenance risk, bus-factor issues, and sensitive-code ownership so teams can prioritize security reviews and remediation.

Core Features & Use Cases

  • Build a bipartite graph of people and files from git history and export nodes and edges as CSV/JSON for Neo4j, Gephi, or other graph consumers.
  • Compute file co-change relationships using Jaccard similarity to cluster files by how they move together and detect ownership drift.
  • Flag sensitive paths with configurable rules, compute bus-factor and orphaned sensitive code, and produce a security-focused summary JSON.
  • Provide bounded LLM-friendly query helpers to fetch people, files, co-change neighbors, communities, and summary slices without loading the full graph.
  • Use cases: security maintainership reviews, CODEOWNERS reality checks, identifying single-owner sensitive hotspots, and importing ownership graphs into graph databases for visualization.

Quick Start

Run the ownership map on your repository to emit CSV/JSON artifacts and a security summary by executing the run_ownership_map.py runner with suitable since, out, and sensitivity options.

Frequently Asked Questions about security-ownership-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find bus-factor risks and sensitive code ownership from git history?▼

You can find bus-factor risks by building a people-to-file ownership topology from git history to identify single-owner sensitive hotspots and orphaned code. The tool flags sensitive paths using configurable rules and outputs a security-focused summary JSON.

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

Yes, you can export git ownership data to Neo4j or Gephi by generating CSV and JSON graph artifacts from the bipartite people-file graph. It also supports networkx-based GraphML outputs for direct import into graph databases and visualization tools.

How does file co-change clustering detect ownership drift in a repository?▼

File co-change clustering detects ownership drift by computing Jaccard similarity edges between files that move together in git commits. This clusters files based on shared commit history, revealing how file maintenance relationships evolve over time.

How do I check if our CODEOWNERS file matches actual git maintenance reality?▼

To check if your CODEOWNERS file matches reality, analyze git history to build an actual people-to-file ownership topology. This surfaces real maintainer activity, highlighting discrepancies between declared ownership and active code maintainers.

Do I need networkx to compute co-change communities and generate GraphML outputs?▼

Yes, you need networkx installed as a dependency to compute co-change Jaccard edges, identify communities, and generate GraphML outputs. The tool relies on networkx for its graph-based analysis and export formats.

What is a git ownership topology and when do I need it for security reviews?▼

A git ownership topology maps people to files based on commit history to reveal maintenance risk and bus-factor issues. You need it for security-oriented maintainer analysis to prioritize code reviews and identify single-owner sensitive code.

Related Skills

Explore More Software Engineering Skills→
lev-oslev-os

security-ownership-map

Analyze git repositories to construct security ownership topology and export CSV/JSON findings.

Official
Advanced
JaimeJunrJaimeJunr
2

security-ownership-map

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

Community
Advanced
RamonsDkaRamonsDka
1

security-ownership-map

Construct bipartite people-files ownership graphs from git history and compute risk metrics.

Community
Advanced
dajneem23dajneem23

security-ownership-map

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

Community
Advanced