security-ownership-map

Analyze git history to compute security ownership and bus factor.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill security-ownership-map-renzo-tognella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/Renzo-Tognella/UniversalThingsForMyAgents/tree/main/skills/security-ownership-map
Command: npx skills add https://github.com/Renzo-Tognella/UniversalThingsForMyAgents --skill security-ownership-map-renzo-tognella

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps analyze security ownership and risk in git repositories by building a security ownership topology and computing bus factor and sensitive-code ownership.

Core Features & Use Cases

  • Security Ownership Topology: Builds a bipartite graph of people and files from git history.
  • Ownership Risk: Computes ownership risk and exports graph artifacts for visualization.
  • Bus Factor: Computes bus factor for sensitive code ownership.
  • Use Case: Ideal for security-focused ownership or bus-factor analysis grounded in git history to identify orphaned sensitive code, security maintainers, or ownership clusters.

Quick Start

Run from the repo root:

python skills/skills/security-ownership-map/scripts/run_ownership_map.py --repo . --out ownership-map-out --since "12 months ago" --emit-commits

Frequently Asked Questions about security-ownership-map

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

FAQPage Schema
How do I analyze git repository security ownership and identify orphaned sensitive code?

Bus factor analysis measures security risk by computing the minimum number of people who must leave a project before sensitive code ownership becomes orphaned. It identifies critical maintainers and quantifies operational risk from git history.

How do I calculate bus factor for sensitive code ownership from git history?

Yes, you need Python 3 and the networkx library to build the security ownership topology graph and compute ownership risk. These dependencies are required to run the analysis script and generate visualization artifacts.

How do I export git ownership data for security audit visualization?

The best way to identify ownership clusters and security maintainers is building a bipartite graph of people and files from git history. This topology maps sensitive code ownership and highlights risk clusters for security audits.

Can I limit git security ownership analysis to a specific time range like the last 12 months?

You should not use git history analysis for security ownership when the repository lacks meaningful commit history or when access control is not tied to commit authorship. It measures contribution topology, not actual deployment permissions.