jayphelps/git-blame-someone-else
Blame someone else for your bad code. observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3862
- days_rel: n/a
- days_push: 1003
- n_releases_24m: 0
Adoption not part of the score
11703 stars · 266 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A joke shell script that rewrites git commit authorship so blame falls on someone else. It's a novelty tool not intended for production repositories.
Use cases
- prank a coworker by faking git blame authorship
- rewrite commit author and committer fields
- demonstrate how git history rewriting works
- change who authored a commit
When to choose
- you want a quick one-command novelty for git blame pranks
- you need a simple shell-based commit author rewrite demo
When to avoid
- any production or shared repository
- you need safe, supported history rewriting tools like git filter-repo
- you require robustness or error handling
Facets
cli-tool · maturity maintenance
version-control cli developer-tools version-control developer-tools cli windows git joke prank shell-script commit-history command-line linux macos
1 source
- readme: https://github.com/jayphelps/git-blame-someone-else · fetched 2026-08-28 · 920c5d310242
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| jayphelps/git-blame-someone-else | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="jayphelps/git-blame-someone-else")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem