Shelling out to git blame in a streaming Node fashion.
Execute git blame for a single line and get a JSON as result
Parse git blame -p output
Execute git blame async and efficiently with results as Map
Shows per-author contribution stats for any file or directory using git blame
Component-level git blame overlay for React projects (Vite & Next.js)
Toggle git-blame annotations in the gutter of atom editor.
```bash npx git-blame-format src/blame-file.ts::BlameLineInfo ```
MCP server for AI-powered code archaeology — git blame, file history, contributor patterns, and related change analysis
Git blame for AI coding agents — record what every agent changed, why, and through which prompts, down to the line.
Hook git blame into jshint
Use git blame to find out who modified a file.
CLI tool for tracing code lines to their originating Pull Requests via git blame
Check for semantic issues in `.git-blame-ignore-revs` -- wrong commit, duplicates, etc.
Starlight plugin that adds per-page contributor lists from local git blame. Host-agnostic (GitHub, GitLab, Codeberg, self-hosted, no remote).
Summarize git blame by author — % line ownership per file and across the repo.
CLI/TUI/GUI source-code scanner with FTS5 search and git blame. (npm wrapper around the prebuilt CodeScan binary.)
Yet another eslint blame (might) with better adaptability. The input is eslint's output with json format (You can see it [here](https://eslint.org/docs/user-guide/formatters/#json)). And it's will run git blame for each eslint report.
git blame game :)
Enrich git blame with PR context — instantly understand why a line of code changed
Git blame + JSHint in your command line
Git blame tells you who. git-why tells you WHY. AI-powered git history explainer.
Find out who last modified a file or line using git blame
``` git blame https://github.com/mafintosh/benny-hill ```
Ultra-fast code debt detection library and CLI
interactive git reblame
Dive into a file's history to find root cause
Generate a listing of who is most likely to be familiar with a file
Parses the git blame porcelain format into a struct.
git blame with the PR number
A program to automatically annotate changes to a file in git(1).
Git blame annotation module for reovim
When one `git blame` is not enough
An alternative to git blame that colors output for easier reading
Git command that shows the blame on the lines that are in conflict
git-spelunk is a terminal based exploration tool for git blame and history, based on the notion of moving in history based on file context
Show git statistics using blame. More metrics are coming.
Who wrote that code? When? Why? Theses are all things we often ask when reading documentation. yard-blame makes it easy to ask.
macblame shows stats about the files tracked by git. It uses the output of 'git blame' and summarize it in a cleaner and intuitive format.
rspec-blame provides a Blame formatter that outputs git blame details for the slowest examples above a profile threshold when profiling with RSpec.
Counting lines of code based upon blame.
A command-line tool that helps you summarize and pretty-print collaborators in a git repository based on contributions Generates stats like: - Number of files changed by a user - Number of commits by user - Lines of code by a user'
Do stuff with git-blame, git-branch, git-log, and git-remote from Ruby.
lolcommits takes a snapshot with your webcam every time you git commit code, and archives a lolcat style image with it. It's selfies for software developers. `git blame` has never been so much fun.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.