skills.rest
open-commander
open-commanderOFFICIAL
Explore all skills by this author →
GitHub

security-ownership-map

...

Updated Feb 9, 2026
Search Tags:#git#security#ownership#graph#risk#CODEOWNERS#co-change
One-click install
npx skills add https://github.com/open-commander/open-commander --skill security-ownership-map-open-commander
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/open-commander/open-commander/tree/main/agents/skills/security-ownership-map
Command: npx skills add https://github.com/open-commander/open-commander --skill security-ownership-map-open-commander

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze Git history to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON artifacts for graph databases and visualization. It helps surface orphaned sensitive code, validate CODEOWNERS alignment, and reveal ownership clusters for risk assessment.

Core Features & Use Cases

  • Build a bipartite graph of people and files from git history and compute ownership risk and sensitive-code ownership.
  • Generate a file co-change graph to cluster files by how they move together, aiding risk and ownership analysis.
  • Export graph artifacts (CSV/JSON) for Neo4j/Gephi and provide summary data for dashboards and automation.

Quick Start

Run the ownership map from the repository root to generate the graphs and the 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 map security ownership and analyze risk from git history?▼

Git history security ownership mapping builds a bipartite graph of people and files to compute bus factor and sensitive-code ownership. This analysis surfaces orphaned sensitive code and reveals risk clusters for assessment.

What is a file co-change graph and how does it help with code risk analysis?▼

A file co-change graph clusters files by how they move together in git history. It helps code risk analysis by identifying tightly coupled files, which aids in understanding ownership boundaries and risk concentration across the codebase.

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

Yes, you can export git ownership data to Neo4j or Gephi. The workflow generates graph artifacts in CSV and JSON formats, providing structured output for graph databases and visualization tools.

How do I check if my CODEOWNERS file aligns with actual git history?▼

To check CODEOWNERS alignment, analyze git history to build an actual security ownership topology of people and files. Comparing this topology against your CODEOWNERS file validates whether declared ownership matches real code contributions.

Does this security ownership map support analyzing specific time windows in git history?▼

Yes, the security ownership map supports analyzing specific time windows in git history. You can configure optional time windows to focus the ownership and risk analysis on a targeted period of codebase changes.

Related Skills

Explore More Data & Analytics Skills→
jovermierjovermier
1

git-history-analyzer

Analyze repository commit history to trace code evolution and ownership.

Community
Basic
ITSaltITSalt
23

nacl-render

Parse Neo4j graph data and render Markdown documents with Mermaid diagrams and Excalidraw boards.

Community
Advanced
alanharrryy-wqalanharrryy-wq
2

security-ownership-map

Analyze git history to map file ownership and compute bus-factor metrics.

Community
Advanced
peteanderson80peteanderson80

security-ownership-map

Analyze git history to map people-to-files ownership and security hotspots.

Community
Advanced