Gordon is status check Github app to enforce and validate about.yaml file specifications in a repository during pull requests to drive code ownership at scale within an organization
-
Updated
Feb 4, 2025 - Python
Gordon is status check Github app to enforce and validate about.yaml file specifications in a repository during pull requests to drive code ownership at scale within an organization
Static analysis binary for agent-sh ecosystem - git history, AST mapping, collectors
🔍 git-author – Identify codebase authorship at a component level, beyond git blame, for better ownership insights.
Kinlyze scans your codebase to find out who really holds the knowledge - and what breaks if they leave. Free CLI, offline by default, with a Dashboard for risk heat maps, ownership profiles, and departure simulations.
VS Code extension to track AI coding assistant usage and maintain code quality. Works with Copilot, Cursor, Claude Code & more. 100% private, local data.
Git history analysis plugin for agentsys - static cached JSON artifact from git history
A tool to script and manage the CODEOWNERS file programmatically, simplifying code ownership rules and generating platform-compatible files.
See your git history like never before. Analyze any repo and generate beautiful HTML dashboards with contribution heatmaps, risk scoring, code ownership, collaboration graphs, and more.
DEV-EYE: A Tool for Monitoring Bus Factor Using Commit History
Generate bounded codebase ownership contexts that agents can load inline or spawn in isolation.
Semantic git queries via MCP. Beyond git log — answer who/what/when/why about any line, file, or branch.
Bus Factor Analyzer - Analyze contributor distribution and calculate Bus Factor for project risk assessment
AI-powered engineering risk intelligence for GitHub repositories. Detect bus factor risk, contributor dependency, and knowledge concentration.
IntelliJ IDEA plugin that analyzes local Git history to find code experts, active maintainers, reviewer suggestions, and ownership risks.
The bus factor, made concrete: the named list of single-owner files in a repo, ranked by risk. Git-history only, language-agnostic, zero deps.
Git Contributor Statistics CLI — scan a repository and see who wrote what, how much they own, and when they were active. Per-author commits, lines, files, active days, and current code ownership.
Interactive TUI for git contribution analysis — impact scoring, code ownership, file coupling, identity deduplication
Open-source Bitbucket Data Center app: path-based Code Owners merge check with subgroup approval thresholds — require N approvals from a specific reviewer group per path.
Perry Code Context is a local-first VS Code extension that shows readable CodeLens context above meaningful symbols in supported source files. It helps answer who uses code, what it calls, who last touched it, which tests look related, and who likely owns the file.
Add a description, image, and links to the code-ownership topic page so that developers can more easily learn about it.
To associate your repository with the code-ownership topic, visit your repo's landing page and select "manage topics."