Your code has
a story.
Commit Canvas turns any repository into chapters, a time machine, and a developer fingerprint — generated from real git data. No cloud. No account. One shareable file.
Six chapters of proof.
Every story is assembled from the same deterministic engine. Here's what it finds — measured on Flask below, on your repository in ten seconds.
A real repository, told properly.
This is a complete Commit Canvas story for Flask — 4,000+ commits, ~15 years of history — embedded below. Scroll inside it. Everything is derived from actual git data.
Point it at a repository. That's the setup.
Point
Any local git repository — yours, private, offline. Or paste a public GitHub URL above and skip the terminal entirely.
./run.sh /path/to/your-project
Read
One pass over real history: commits, merges, tags, authors, files, lines, languages. Every claim in the story is grounded in a timestamp.
→ reading history
→ finding turning points
Share
A single HTML file that works offline forever — plus downloadable share cards sized for X, LinkedIn and stories. Screenshot the certificate if that's your thing.
→ story.html ✓
Statistics tell you what.
Stories tell you why.
GitHub gives you bar charts. Commit Canvas gives you “The project went quiet for 43 days” — and proves it with the commit that ended the silence.
The story engine
Your history becomes chapters — The Beginning, The Sprint, The Silence, The Comeback, The Launch. Every line is derived from real timestamps and counts, never invented.
deterministicRepository time machine
Scrub or press play and watch the project assemble itself: commits appearing, contributors joining, files and languages growing, month by month.
the flagshipDeveloper fingerprint
The Night Builder. The Sprinter. The Shipper. Your git behavior — favorite hours, streaks, bursts, message style — distilled into one honest archetype.
git behavior, not psychologyRoast my git & share cards
Affectionately brutal observations backed by real numbers — plus downloadable cards built for feeds. The certificate is designed to be screenshotted.
viral by designEvery history has a shape.
We name it honestly.
The engine reads velocity, gaps and comebacks, then assigns the arc that the timestamps actually support — never one they don't.
Fresh Start
This story is just opening — commits and counting.
The Sprint
Built in bursts of deep focus — the history remembers every surge.
The Climb
It started quiet and kept accelerating. Momentum you can see.
The Return
It went quiet. Then it came back. Projects don't do that by accident.
The Marathon
No drama, no spikes — just showing up, month after month.
The Slow Fade
The early energy was real. What comes next is the interesting part.
The Journey
Quiet parts, loud parts, and everything in between.
Your repository never leaves your machine.
The CLI reads your local .git folder and writes one HTML file. No account, no API key, no telemetry, no server. The output file makes zero network requests — open it on a plane.
The instant web version above reads public repositories through GitHub's API in your browser — nothing is stored, because there is no backend to store it.
# clone once, use forever git clone https://github.com/ahmadrrrtx/commit-canvas cd commit-canvas # any repo, private or public ./run.sh /path/to/your-project # → story.html — open it. scroll slowly.
What is Commit Canvas, exactly?
What is Commit Canvas?
Commit Canvas is an open-source tool that turns a git repository into a cinematic, interactive story — chapters, a time machine, a developer fingerprint and share cards — generated from real commit data. The output is a single self-contained HTML file.
Who is it for?
Developers who want to see — and show — how a project actually evolved: maintainers, portfolio builders, teams writing retrospectives, and anyone who has ever wondered what their commit history says about how they work.
How does it work?
The CLI reads your local .git folder in a single pass (commits, merges, tags, authors, per-file line changes) and a deterministic engine derives the story — no AI, no guessing. The web version does the same analysis in your browser through the GitHub API for public repositories.
Does it require an account?
No. There is no sign-up, no login, and no API key. The CLI works fully offline.
Does Commit Canvas store my repository data?
No. There is no backend and no database. The CLI writes one HTML file to your disk. The web version runs entirely in your browser — the only network calls are to GitHub's public API while analyzing a public repo. Generated story files contain commit metadata (authors, dates, messages) — what you choose to share is up to you.
Can it analyze private repositories?
Yes — with the local CLI, which reads the repository on your machine and never sends anything anywhere. The browser version only works with public GitHub repositories.
What can I export?
PNG share cards (X/LinkedIn, square, 9:16 story, README banner), an animated GIF of the time machine, a WebM video, an SVG timeline, a README markdown block, and the full self-contained story.html.
Is it open source?
Yes — MIT licensed. The whole product is on GitHub.
Does it need an API key or an account?
No key, no sign-in. The web version uses GitHub's public anonymous API. The CLI reads the local .git directory and works fully offline.
Which git providers are supported?
Any of them. The CLI works on any local git repository — GitHub, GitLab, Bitbucket, Gitea, or a folder no server has ever seen. The web version accepts public GitHub URLs.
Who created Commit Canvas?
Muhammad Ahmad — a developer building tools at the intersection of developer experience, data storytelling and open source.
Your next README
is already in your .git folder.
One command. One file. A story you didn't know you had.
cd commit-canvas && ./run.sh /path/to/repo