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.

4.57x

Quality

88%

Does it follow best practices?

Impact

96%

4.57x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Preview

This is a new way to view eval results. We're still working on it, so the layout may change.

Run	Type	Date	Status
baseline vs usage-spec With / without context 7 months ago Completed	With / without context	7 months ago	Completed

Eval run

019cc90f-4ad9-70f5-9709-df15afc6f6c9

Run 7 months ago

Stats are not available yet

The run is available. Its result stats will appear here when they are ready.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/security-ownership-map/SKILL.md
Commit: ddcaa2a

Evaluated: 7 months ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Security Ownership Audit for Backend Service Payment Code Ownership Audit with Custom Sensitivity Rules Quarterly Ownership Evolution Report for Network Module

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.