skills.rest
Moliboy5000
Moliboy5000COMMUNITY
Explore all skills by this author →
GitHub

security-ownership-map

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

Updated Mar 14, 2026
Search Tags:#git#code analysis#security#maintainability#ownership#risk assessment#bus factor
One-click install
npx skills add https://github.com/Moliboy5000/.claude --skill security-ownership-map-moliboy5000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/Moliboy5000/.claude/tree/main/skills/security-ownership-map
Command: npx skills add https://github.com/Moliboy5000/.claude --skill security-ownership-map-moliboy5000

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill analyzes git history to identify who owns which files, compute the bus factor (how many people are needed to disrupt a project), and pinpoint risks associated with sensitive code.

Core Features & Use Cases

  • Ownership Mapping: Creates a detailed map of people-to-file ownership based on commit history.
  • Bus Factor Calculation: Determines the minimum number of people required to maintain critical parts of the codebase.
  • Sensitive Code Analysis: Identifies ownership and potential risks for files tagged as sensitive (e.g., auth, crypto).
  • Graph Export: Generates data for visualization in tools like Neo4j or Gephi.
  • Use Case: A security team can use this to check if sensitive cryptographic code is owned by too few people or if ownership has drifted from the CODEOWNERS file, highlighting potential security blind spots.

Quick Start

Run the security ownership map skill on the current repository to analyze commits from the last 12 months.

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 security bus factor for a git repository?▼

You can perform a CODEOWNERS reality check by analyzing git history to map actual file ownership and comparing it against declared CODEOWNERS. This reveals ownership drift and flags sensitive code hotspots lacking proper maintainer coverage.

How does sensitive code ownership analysis work using git history?▼

You can export git ownership and risk assessment data in CSV or JSON formats. These structured exports are suitable for importing into graph databases like Neo4j or visualization tools like Gephi to map security ownership topology.

Can I use networkx to analyze security maintainer identification in git?▼

You can use networkx to analyze security maintainer identification by modeling git ownership clusters as a graph. This helps detect sensitive code hotspots and orphaned code areas where critical security maintainers are missing or too sparse.

Does this security ownership analysis work for general maintainer lists?▼

This security ownership analysis does not work for general maintainer lists or non-security ownership queries. It triggers specifically for security-oriented ownership and bus-factor analysis grounded in git history, focusing on sensitive code risks.

Related Skills

Explore More Software Engineering Skills→
myapihqmyapihq
83

my-git-api

Manage hosted git repositories via API without local clones.

Official
Advanced
northseadlnorthseadl

security-ownership-map

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

Community
Advanced
tech-leads-clubtech-leads-club
5.0k

security-ownership-map

Analyze git history to build security ownership graphs linking people to files.

Official
Advanced
heyzudeheyzude
4

security-ownership-map

Analyze git repositories to generate security ownership topology and bus factor data.

Community
Advanced