security-ownership-map

Analyze git history to build security ownership graphs and compute bus factor.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/oiagorodrigues/qcontabil --skill security-ownership-map-oiagorodrigues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/oiagorodrigues/qcontabil/tree/main/.cursor/skills/security-ownership-map
Command: npx skills add https://github.com/oiagorodrigues/qcontabil --skill security-ownership-map-oiagorodrigues

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze git history to surface security ownership relationships between people and files, identify sole maintainers and risky hotspots, and provide a governance-ready view of ownership.

Core Features & Use Cases

  • Build a bipartite ownership graph (people ↔ files) from commit history and extract a bus factor and sensitive-code hotspots.
  • Generate a co-change graph to reveal how files move together, helping to cluster ownership and detect drift.
  • Export artifacts (CSV/JSON) for graph databases (Neo4j/Gephi) and enable bounded queries via a helper tool.

Quick Start

Run the ownership map script on your repository to generate the graph 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 the bus factor for my repository using git history?

This Skill calculates the bus factor by analyzing git history to build a bipartite ownership graph between people and files. It processes commit data to identify sole maintainers and compute ownership risk metrics.

What is a co-change graph and how does it help identify security ownership drift?

A co-change graph reveals how files move together in git history. Generating this graph helps cluster ownership relationships and detect drift in sensitive code areas across your repository.

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

Yes, you can export the security ownership topology to graph databases like Neo4j and Gephi. The Skill generates CSV and JSON artifacts from git history to enable visualization and bounded queries.

Does this ownership analysis tool work on large codebases with orphaned sensitive code?

Yes, this ownership analysis applies to codebases of any size, including those with orphaned sensitive code. It maps security ownership and identifies risky hotspots regardless of repository scale.

Do I need networkx installed to generate security ownership graphs from git history?

Yes, networkx is required to generate the security ownership graphs from git history. The Skill uses this Python library to build the graph outputs and compute the ownership topology metrics.

What is the best way to identify sole maintainers of sensitive code in a repository?

The best way is mapping git history to a security ownership topology between people and files. This exposes sole maintainers and risky hotspots to provide a governance-ready view of ownership risk.