security-ownership-map Skill
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for exam Published by openai in skills.
What is security-ownership-map Skill?
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for exam Published by openai in skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Data analysis
- Security review use cases
- Data analysis use cases
Technical details
- Install or run with Copy skill directory
When to use security-ownership-map Skill
- Use it for security review.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/skills
- Skill file: skills/.curated/security-ownership-map/SKILL.md
What it does
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for exam
Skill instructions
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: bash pip install networkx Workflow 1. Scope the repo and time window (optional --since/--until). 2. Decide sensitivity rules (use defaults or provide a CSV config). 3. Build the ownership map with scripts/runownershipmap.py (co-change graph is on by default; use --cochange-max-files to ignore supernode commits). 4. Communities are computed by default; graphml output is optional (--graphml). 5. Query the outputs with scripts/queryownership.py for bounded JSON slices. 6. Persist and visualize (see references/neo4j-import.md). By default, the co-change graph ignores common “
Explore related resources
Frequently asked questions
What is security-ownership-map?
security-ownership-map is a open-source AI agent skill with Copy skill directory. Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization.
Who is security-ownership-map best for?
security-ownership-map is best for reusing agent instructions, scripts, and references, security review workflows, data analysis workflows.
How do I install security-ownership-map?
Install or run security-ownership-map using Copy skill directory. Check security-ownership-map for the latest setup command.
Is security-ownership-map actively maintained?
security-ownership-map may need a closer maintenance check before production use.
Auto-fetched from GitHub.
