skills.rest
jscraik
jscraikCOMMUNITY
Explore all skills by this author →
Website𝕏@jscraikGitHub

security-ownership-map

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

8|4|Updated Jan 15, 2026
Search Tags:#git#code analysis#security#ownership#risk assessment#bus factor
One-click install
npx skills add https://github.com/jscraik/Agent-Skills --skill security-ownership-map-jscraik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/jscraik/Agent-Skills/tree/main/product/security/security-ownership-map
Command: npx skills add https://github.com/jscraik/Agent-Skills --skill security-ownership-map-jscraik

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 helps identify who owns which files in a code repository, calculates the "bus factor" (how many people are critical for a file's maintenance), and highlights sensitive code that might be at risk due to low ownership.

Core Features & Use Cases

  • Ownership Mapping: Creates a graph of people and files based on git history.
  • Risk Assessment: Computes bus factor and identifies sensitive code with low ownership.
  • Artifact Generation: Exports data as CSV, JSON, and graph formats for visualization (e.g., Neo4j, Gephi).
  • Use Case: A security team needs to understand who is responsible for critical authentication code. This Skill can analyze the git history to show all developers who have touched authentication files, calculate the bus factor for those files, and flag any sensitive files with only one or zero recent contributors.

Quick Start

Run the security ownership map script for the current repository, analyzing 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 bus factor and identify sensitive code risk in a git repository?▼

To calculate bus factor and identify sensitive code risk in a git repository, analyze git history to map file ownership and flag critical files with low recent contributor counts.

What is a git ownership map and how does it help with security risk assessment?▼

A git ownership map visualizes developer-to-file relationships based on commit history, helping security teams assess risk by highlighting sensitive code maintained by very few contributors.

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

Yes, you can export git code ownership data to Neo4j or Gephi by generating CSV, JSON, and graph artifacts from the repository's commit history for direct visualization imports.

Does this security ownership analysis require networkx to process git history?▼

Yes, security ownership analysis requires networkx to process git history, build the graph of people and files, and compute the bus factor metrics for sensitive code risk assessment.

How do I map security ownership for authentication files using git commit history?▼

Map security ownership for authentication files by analyzing git commit history to list all developers who touched those files and calculating the bus factor to identify maintenance risks.

Related Skills

Explore More Software Engineering Skills→
ShmurdocShmurdoc

retro

Analyze git commit history and code quality metrics to generate engineering retrospective reports.

Community
Advanced
pingqLINpingqLIN

security-ownership-map

Analyzes git history to map people-to-files ownership and detect security risks in codebases.

Community
Advanced
guhans6guhans6

security-ownership-map

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

Community
Advanced
lidge-junlidge-jun
5

security-ownership-map

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

Community
Advanced