Execute git blame for a single line and get a JSON as result
Shelling out to git blame in a streaming Node fashion.
Parse git blame -p output
Recursive blame for Git
Social blame tool for Git
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.
Execute git blame async and efficiently with results as Map
CLI that auto-detects bulk-change commits and manages .git-blame-ignore-revs file
Shows per-author contribution stats for any file or directory using git blame
Component-level git blame overlay for React projects (Vite & Next.js)
AI Blame ========
```bash npx git-blame-format src/blame-file.ts::BlameLineInfo ```
> Blame smarter. Ramp up faster.
Local-first Git history UI with natural-language search, PR grouping, time travel, blame, and optional AI.
MCP server for AI-powered code archaeology — git blame, file history, contributor patterns, and related change analysis
Toggle git-blame annotations in the gutter of atom editor.
Enrich git blame with PR context — instantly understand why a line of code changed
I just learn to create my first react component library. Please don't blame :D
**Blame** is a powerful project generator CLI tool that helps you quickly scaffold your projects using popular frameworks. Whether you're starting a new Node.js app or a React application, **Blame** makes the setup a breeze! 🎉
``` sh ~ remote-blame github.com/wangzuo/remote-blame/8c3bb4217f13657e078891cc9e2a049407afd182/__tests__/blame.js+5 { "author": "wangzuo", "title": "add jest", "date": "2017-02-06T14:18:01Z" } ```
Git blame for AI coding agents — record what every agent changed, why, and through which prompts, down to the line.
Git integration for ProvenanceKit - Track commits, blame analysis, AI detection, and GitHub integration
AI pre-commit guardian. Blame-aware. Auto-fix. Learns.
Contains support for the nuclide-blame feature.
Extract provenance from AI agent execution traces - like git blame, but for AI-assisted edits
Track which prompts created or modified code lines
Line-by-line authorship tracking for revisioned text
Parses the git blame porcelain format into a struct.
monitord-exporter ... let prometheus know how happy your systemd is! 😊
AXON — the formal cognitive language: a deterministic, proof-carrying AI runtime. Native Rust lexer/parser/type-checker/IR generator (re-exported from axon-frontend) plus the runtime: typed channels (π-calculus mobility, capability extrusion), algebraic effects via Free Monad CPS handlers, lease kernel + reconcile loop, the Epistemic Security Kernel, Trust Types, Proof-Carrying Code (independently verifiable proof objects), and the closed-catalog extension mechanism. Crate publishes as `axon-lang`; library import is `use axon::*` so existing call sites keep working unchanged.
The all-seeing repository analyzer
A cli tool that provides search results in a git repo using the author as a search key
Track TODO/FIXME/HACK comments with git-aware diff and CI gate
A simple cli tool to find out who last edited files or directories of git repositories
git blame with the PR number
Gild — interactive git contribution analyzer with fair impact scoring
see who's responsible for gem crimes
Analyzes Test Kitchen logs to help optimize boot times, recipes, and individual resources.
rspec-blame provides a Blame formatter that outputs git blame details for the slowest examples above a profile threshold when profiling with RSpec.
Who wrote that code? When? Why? Theses are all things we often ask when reading documentation. yard-blame makes it easy to ask.
'git blame' added Brakeman JSON warnings. We have all the information at brakeman security warnings. But, Don't have a blame option for which developer done the vulnerabilities.Below is example. { .... 'blame': 'xxxxxxxxxxxxx (developer_name 2019-07-17 20:59:12 +0530 4226) params.require(:users).permit! ' ... }
Recursive blame.
Git command that shows the blame on the lines that are in conflict
When one `git blame` is not enough
An alternative to git blame that colors output for easier reading
When one `hg blame` is not enough
Similar to ActiveRecord::Timestamp, this gem provides a blame datetime and user for create/update modifications to records. Configured models will be blamed when creating or updating, and the blame can cascade to associated models on create, update or delete. Currently, this gem is intended for use with Devise.
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
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.