security-ownership-map

Analyze git history to map people-to-files ownership and compute bus factor.

3|Updated Jan 14, 2022
One-click install
npx skills add https://github.com/bingran-you/bingran-you --skill security-ownership-map-bingran-you
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/bingran-you/bingran-you/tree/main/repo-skills/security-ownership-map
Command: npx skills add https://github.com/bingran-you/bingran-you --skill security-ownership-map-bingran-you

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Git history can obscure who owns which parts; this skill builds a stable map of people-to-files ownership, highlights bus-factor risks, and surfaces sensitive hotspots to guide audits and responsibilities.

Core Features & Use Cases

  • Build a bipartite graph of people and files from git history and compute ownership risk, bus factor, and sensitive hotspots.
  • Export artifacts (CSV/JSON) for graph databases and visualization tools like Neo4j/Gephi; generate a co-change graph to cluster files by movement.
  • Support configurable time windows, sensitivity rules, and dependency-free data extraction with optional community detection.

Quick Start

Run the ownership map against your repository to generate the CSV/JSON artifacts and security insights.

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 calculate bus factor from git history?

You can map security ownership from git history by building a bipartite graph of people and files, computing bus factor risks, and surfacing sensitive hotspots. It exports CSV and JSON artifacts for downstream querying and visualization.

What is a bus factor analysis and how does it identify security hotspots?

A bus factor analysis evaluates repository risk by mapping people-to-files ownership from git history to identify areas where knowledge is concentrated. It highlights sensitive hotspots and ownership risks to guide security audits and responsibility assignments.

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

Yes, you can export git ownership data to Neo4j or Gephi. The analysis generates people.csv, files.csv, and edges.csv artifacts, alongside a co-change graph, which are formatted for direct import into graph databases and visualization tools.

Does the security ownership analysis support custom time windows and sensitivity rules?

Yes, security ownership analysis supports configurable time windows and custom sensitivity rules. This allows you to scope git history evaluations to specific periods and define hotspot criteria for targeted risk assessment.

Do I need networkx to run the git co-change graph analysis?

No, networkx is optional. The skill provides dependency-free data extraction for basic git history mapping, but requires networkx if you want to enable optional community detection and advanced co-change graph clustering.