skills.rest
SameerG7
SameerG7COMMUNITY
Explore all skills by this author →
GitHub

security-ownership-map

Analyzes Git history to build bipartite ownership maps of people and files.

Updated Aug 23, 2026
Search Tags:#security#analytics#ownership#graph#git-history#networkx#cochange
One-click install
npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill security-ownership-map-sameerg7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/SameerG7/synthesis-hackathon-aibom/tree/main/.codex/skills/security-ownership-map
Command: npx skills add https://github.com/SameerG7/synthesis-hackathon-aibom --skill security-ownership-map-sameerg7

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Build a bipartite graph linking people and files from git history to surface ownership risk and bus-factor insights.

Core Features & Use Cases

  • Graph construction: bipartite graph of people and files from commit history.
  • Ownership risk scoring and bus-factor metrics to identify critical maintainers.
  • Co-change graph and clustering to reveal file movement and hotspots.
  • Output artifacts: CSV/JSON ready for graph databases and visualization, including optional cochange graphs.
  • Use-case: Audit security-sensitive components to identify owners and drift across a large codebase.

Quick Start

From the repository root, run the ownership map script to generate the ownership artifacts.

Frequently Asked Questions about security-ownership-map

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

FAQPage Schema
How do I calculate bus factor and code ownership risk from git history?▼

Calculate bus factor and ownership risk by parsing git history to build a bipartite graph linking people to files, then scoring ownership concentration and identifying sensitive hotspots across repositories.

How do I generate a co-change graph to visualize file dependencies in a monorepo?▼

Generate a co-change graph by analyzing commit history with configurable thresholds and clustering to reveal file movement patterns and community-level hotspots across monorepos.

Does this git ownership analysis require networkx to build the graph?▼

Yes, building the security ownership graph and performing community-level clustering requires the networkx dependency to construct the bipartite relationships and analyze the network structure.

What output formats are generated when mapping code ownership and security hotspots?▼

Mapping code ownership generates CSV and JSON artifacts including people.csv, files.csv, edges.csv, summary.json, and optional cochange_edges.csv ready for graph databases and visualization.

Can I audit security-sensitive components and track ownership drift over a specific date range?▼

Yes, you can audit security-sensitive components and track ownership drift by applying date windows and sensitive-path rules to the git history analysis to isolate changes within specific periods.

What is the best way to identify critical maintainers and ownership bottlenecks in a large codebase?▼

The best way to identify critical maintainers is by constructing a bipartite graph from commit history to quantify bus-factor metrics and highlight ownership bottlenecks in sensitive codebase areas.

Related Skills

Explore More Data & Analytics Skills→
EstomEstom

security-ownership-map

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

Community
Advanced
open-commanderopen-commander

security-ownership-map

...

Official
Advanced
Ed1s0nZEd1s0nZ
5.6k

vulnerability-assessment

Assess system and application vulnerabilities with CVSS risk scoring.

Community
Advanced
RamonsDkaRamonsDka
1

security-ownership-map

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

Community
Advanced