security-ownership-map

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

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/northseadl/skillwisp --skill security-ownership-map-northseadl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/northseadl/skillwisp/tree/main/skills/%40openai/security-ownership-map
Command: npx skills add https://github.com/northseadl/skillwisp --skill security-ownership-map-northseadl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify security risks in code by analyzing who owns which files, calculating the bus factor (how many people are critical to maintain a file), and highlighting sensitive code that might be neglected.

Core Features & Use Cases

  • Ownership Topology: Builds a graph of people and files based on git history.
  • Bus Factor Calculation: Computes the bus factor for files and identifies hotspots.
  • Sensitive Code Analysis: Flags code in sensitive areas (auth, crypto, secrets) with low ownership or stale history.
  • Graph Export: Outputs data for visualization in tools like Neo4j or Gephi.
  • Use Case: A security team can use this to check if critical security modules have a low bus factor, indicating a high risk if key maintainers leave, or to find sensitive code that hasn't been touched in years.

Quick Start

Run the security ownership map script on the current repository to generate an ownership map and summary.

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 for files in a git repository?

To calculate bus factor in a git repository, this Skill analyzes git history to build an ownership topology of people and files, computing how many maintainers are critical to each file. It identifies hotspots where low ownership creates maintenance risk.

How can I find sensitive code with low ownership or stale history?

Sensitive code in areas like auth, crypto, or secrets is flagged by analyzing git history for files with low ownership or stale commit activity. This highlights neglected security modules that may lack active maintainers or recent updates.

What is a security ownership topology and how does it work?

A security ownership topology is a graph mapping people to files based on git history. It shows who maintains sensitive code areas and reveals ownership clusters, helping teams visualize concentration of security knowledge and identify orphaned code.

Can I export git ownership analysis data to Neo4j or Gephi?

Yes, git ownership analysis data is exported in CSV and JSON formats suitable for graph databases and visualization tools like Neo4j or Gephi. This allows you to import ownership topology and bus factor data for interactive graph exploration.

Do I need networkx installed to run the bus factor analysis?

Yes, networkx is a required dependency for constructing the ownership topology graph and computing bus factor metrics. The Skill relies on it to build the people-to-files graph from git history data.