skills.rest
bl1nk-bot
bl1nk-botOFFICIAL
Explore all skills by this author →
GitHub

security-ownership-map

Build a security ownership map from git history to identify risk hotspots.

3|Updated Feb 13, 2026
Search Tags:#security#analytics#ownership#graph#git-history#bus-factor#code-ownership
One-click install
npx skills add https://github.com/bl1nk-bot/skills-cli --skill security-ownership-map-bl1nk-bot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/bl1nk-bot/skills-cli/tree/main/skills/security-ownership-map
Command: npx skills add https://github.com/bl1nk-bot/skills-cli --skill security-ownership-map-bl1nk-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This tool automates the extraction of ownership and risk signals from Git history by building a security-focused ownership map that highlights who owns code, which areas are high-risk, and where bus factor concerns exist.

Core Features & Use Cases

  • Build a bipartite graph of people and files from commit history to reveal who touched what.
  • Compute ownership risk, bus factor hotspots, and sensitive-code exposure with exportable artifacts for graph databases and visualization.
  • Query outputs to surface orphaned sensitive code, hidden owners, and community maintainers for risk assessment and remediation.

Quick Start

Run the ownership map builder from the repository root to generate the ownership graph artifacts in 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 map code ownership and find risk hotspots from git history?▼

Map code ownership from git history by building a bipartite graph of people and files using commit data. This process identifies ownership, surfaces risk hotspots, and calculates the bus factor for sensitive code areas.

How do I detect orphaned sensitive code in a repository?▼

Detect orphaned sensitive code by querying the generated ownership map outputs like files.csv and summary.json. This surfaces files lacking clear ownership and identifies hidden owners or community maintainers for security remediation.

What is the best way to calculate the bus factor for sensitive code?▼

Calculate the bus factor for sensitive code by analyzing commit history to build an ownership map. This approach clusters related files by ownership patterns and highlights areas where knowledge concentration creates risk.

What output formats does the git ownership analysis generate?▼

The git ownership analysis generates CSV and JSON outputs such as people.csv, files.csv, and summary.json. These artifacts contain the computed ownership risk data and can be exported to graph databases for visualization.

Related Skills

Explore More Software Engineering Skills→
lev-oslev-os

security-ownership-map

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

Official
Advanced
Sacred-GSacred-G
2

security-ownership-map

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

Community
Advanced
voidrotvoidrot

sast-configuration

Configure SAST tools like Semgrep, CodeQL, and SonarQube for CI/CD pipelines.

Community
Intermediate
ecosyste-msecosyste-ms
1

commits

Analyze commit history and contributor statistics for public repositories.

Official
Intermediate