skills.rest
lev-os
lev-osOFFICIAL
Explore all skills by this author →
GitHub

security-ownership-map

Analyze git repositories to construct security ownership topology and export CSV/JSON findings.

Updated Feb 13, 2026
Search Tags:#git#code analysis#security#ownership#risk assessment#graph database#bus factor
One-click install
npx skills add https://github.com/lev-os/lev-content --skill security-ownership-map-lev-os
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/lev-os/lev-content/tree/main/sources/skills/security-ownership-map
Command: npx skills add https://github.com/lev-os/lev-content --skill security-ownership-map-lev-os

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of understanding who owns what code, especially sensitive code, and assessing the associated risks like bus factor and potential ownership drift.

Core Features & Use Cases

  • Security Ownership Topology: Builds a graph of people-to-file ownership based on git history.
  • Bus Factor & Sensitive Code Analysis: Computes bus factor and identifies ownership of sensitive code.
  • Graph Export: Exports data in CSV/JSON formats suitable for graph databases (Neo4j) and visualization tools (Gephi).
  • Use Case: Identify sensitive code files with a low bus factor (few owners) or check if CODEOWNERS accurately reflects actual development activity.

Quick Start

Run the security ownership map skill to analyze the current repository for the last 12 months, outputting the results to a directory named 'ownership-map-out'.

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 a git repository?▼

You can calculate the bus factor for a git repository by analyzing its commit history to build a people-to-file ownership graph. This Skill scopes analysis by repository and time window to compute the bus factor for sensitive code.

What is code ownership drift and how does git history analysis detect it?▼

Code ownership drift occurs when actual development activity diverges from documented ownership. By analyzing git history and clustering files via co-change graphs, this Skill detects ownership patterns and identifies sensitive files with low ownership concentration.

Can I export git commit ownership data for visualization in Neo4j or Gephi?▼

Yes, you can export git commit ownership data for graph databases like Neo4j and visualization tools like Gephi. This Skill outputs the security ownership topology in CSV and JSON formats to facilitate external graph analysis.

Does the code ownership analysis exclude automated bot commits and glue files?▼

Yes, the code ownership analysis excludes common glue files and automated bot commits by default. This ensures the calculated bus factor and sensitive code ownership topology accurately reflect actual human developer activity.

How do I configure sensitive code rules for a repository risk assessment?▼

You configure sensitive code rules to scope your repository risk assessment. This allows the security ownership topology to specifically target and calculate the bus factor for the sensitive code files that matter most to your project.

Related Skills

Explore More Software Engineering Skills→
jovermierjovermier
1

git-history-analyzer

Analyze repository commit history to trace code evolution and ownership.

Community
Basic
JaimeJunrJaimeJunr
2

security-ownership-map

Generate a people-to-files ownership topology with risk hotspots from git history.

Community
Advanced
MercurykzMercurykz

security-ownership-map

Build a security ownership map from git history with networkx.

Community
Advanced
jaypatrickjaypatrick

security-ownership-map

Generate a security-ownership map from Git history, outputting CSV/JSON artifacts.

Community
Advanced