explaingit

haruko386/repositoryblame

Analysis updated 2026-07-08 · repo last pushed 2026-07-07

PythonAudience · developerComplexity · 2/5ActiveSetup · easy

TLDR

A GitHub Actions tool that scans your codebase with git blame and generates an SVG chart showing what percentage of code each contributor wrote, so you can display contributor breakdown directly in your README.

Mindmap

mindmap
  root((repo))
    What it does
      Generates contributor charts
      Outputs SVG image
      Runs in GitHub Actions
    How it works
      Uses git blame
      Resolves GitHub usernames
      Pushes to a branch
    Use cases
      Show contributors in README
      Visualize team work distribution
      Highlight open-source community
    Configuration
      Set contributor thresholds
      Filter out directories
      Limit top contributors
    Tech stack
      Python
      GitHub Actions
      Git blame
      GitHub API
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Add a contributor breakdown chart to your open-source project's README.

USE CASE 2

Visualize how work is distributed across your team members.

USE CASE 3

Highlight top contributors with avatars while bundling minor contributors into a secondary section.

What is it built with?

PythonGitHub ActionsGitSVG

How does it compare?

haruko386/repositoryblame0xhassaan/nn-from-scratcha-little-hoof/dsr
Stars00
LanguagePythonPythonPython
Last pushed2026-07-07
MaintenanceActive
Setup difficultyeasymoderatehard
Complexity2/54/55/5
Audiencedeveloperdeveloperresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Requires adding a configuration file and GitHub Actions workflow to your repository, plus write permissions to push the generated SVG to a branch.

No license information was provided in the repository explanation, so the licensing terms are unknown.

In plain English

RepositoryBlame generates a visual chart showing what percentage of your codebase each contributor wrote. You get an SVG image that you can drop right into your project's README, so visitors instantly see who built what. The tool runs inside GitHub Actions, so you just add a configuration file to your repository and it handles the rest. It scans your source files using git blame, which figures out who last touched each line of code. Then it cross-references each change with GitHub's commit data to resolve real usernames and avatars. The final chart is pushed to a separate branch in your repo, and you link to it like any other image. This is useful for open-source maintainers who want to highlight their community, or for team leads who want a quick visual of how work is distributed. For example, a project with dozens of contributors can show the top ten as named entries with avatars, while everyone below a threshold (say, 0.8%) gets bundled into a smaller secondary area. You can configure how many contributors appear in each section and filter out directories like node_modules or vendor so the stats reflect meaningful code, not dependencies. One thing worth noting is that the whole approach relies on git blame, so it credits whoever made the most recent change to each line, not necessarily the original author. If someone reformats a file, they might show up as the contributor for those lines. The README doesn't discuss this tradeoff, but it's inherent to how the underlying tool works. The setup also requires write permissions to push the generated image to a branch, which is standard for this kind of automation.

Copy-paste prompts

Prompt 1
Set up RepositoryBlame in my GitHub repo: write the GitHub Actions workflow YAML and configuration file to generate an SVG contributor chart and push it to a separate branch.
Prompt 2
Help me configure RepositoryBlame to show the top 10 contributors with avatars and bundle everyone below 1% into a secondary section, while filtering out node_modules and vendor directories.
Prompt 3
Write the markdown snippet to embed the RepositoryBlame SVG chart into my README so it displays the contributor breakdown for my project.
Prompt 4
Explain how RepositoryBlame uses git blame and GitHub commit data to calculate contributor percentages, and what the limitations are regarding crediting the original author versus the last person to touch a line.

Frequently asked questions

What is repositoryblame?

A GitHub Actions tool that scans your codebase with git blame and generates an SVG chart showing what percentage of code each contributor wrote, so you can display contributor breakdown directly in your README.

What language is repositoryblame written in?

Mainly Python. The stack also includes Python, GitHub Actions, Git.

Is repositoryblame actively maintained?

Active — commit in last 30 days (last push 2026-07-07).

What license does repositoryblame use?

No license information was provided in the repository explanation, so the licensing terms are unknown.

How hard is repositoryblame to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is repositoryblame for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.