security-ownership-map
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 example: orphaned sensitive code, security maintainers, CODEOWNERS reality checks for risk, sensitive hotspots, or ownership clusters). Do not trigger for general maintainer lists or non-security ownership questions.
Pinned to revision 4e4fe02df5f4, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/security-ownership-map/SKILL.md
- skills/security-ownership-map/LICENSE.txt
- skills/security-ownership-map/agents/openai.yaml
- skills/security-ownership-map/metadata.json
- skills/security-ownership-map/references/neo4j-import.md
- skills/security-ownership-map/scripts/build_ownership_map.py
- skills/security-ownership-map/scripts/community_maintainers.py
- skills/security-ownership-map/scripts/query_ownership.py
- skills/security-ownership-map/scripts/run_ownership_map.py
Every link opens the file at its source, pinned to the revision this page describes.