Office & DocumentsAdvanced
security-ownership-map
Map people-to-file ownership, compute bus factor, and identify risks
Developer Setup
Setup & Installation
bash
npx skills add https://github.com/openai/skills --skill security-ownership-mapnpx skills add https://github.com/openai/skills --skill security-ownership-mapOr paste this URL into your assistant to install:
Overview
What This Skill Does
Map people-to-file ownership, compute bus factor, and identify risks
Application
When to use this Skill
- Integrating security ownership map into your development workflow.
- Following best practices for map people-to-file ownership, compute bus factor, and identify risks.
- Automating repetitive tasks with AI-assisted tooling.
- Building production-grade applications with proper standards.
- Debugging and troubleshooting common implementation issues.
Documentation
Show Skills.md file
Security Ownership Map
Overview
Build a bipartite graph of people and files from git history, then compute ownership risk and export graph artifacts for Neo4j/Gephi. Also build a file co-change graph (Jaccard similarity on shared commits) to cluster files by how they move together while ignoring large, noisy commits.
Requirements
- Python 3
networkx(required; community detection is enabled by default)
Install with:
pip install networkx
Workflow
- Scope the repo and time window (optional
--since/--until). - Decide sensitivity rules (use defaults or provide a CSV config).
- Build the ownership map with
scripts/run_ownership_map.py(co-change graph is on by default; use--cochange-max-filesto ignore supernode commits). - Communities are computed by default; graphml output is optional (
--graphml). - Query the outputs with
scripts/query_ownership.pyfor bounded JSON slices. - Persist and visualize (see
references/neo4j-import.md).
Lines 1 - 25 of 201
Recommendations