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. Use 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 use for general maintainer lists, non-security own

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• rea-changelog-update 456,474 ★
  Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified cont
• git-guardrails-claude-code 323,337 ★
  Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before t
• pr 323,337 ★
  Use when writing a PR body.
• setup-matt-pocock-skills 323,337 ★
  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain
• setup-pre-commit 323,337 ★
  Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use w