I Turned Your GitHub Profile Into a Detective Case File (And the Verdict Might Hurt)
Your GitHub profile is a public confession booth. Repos count. Followers. That bio you wrote at 1 a.m. and never fixed. Languages you claim to "love" while secretly opening node_modules like a crime scene every Tuesday.
Your GitHub profile is a public confession booth.
Repos count. Followers. That bio you wrote at 1 a.m. and never fixed. Languages you claim to "love" while secretly opening node_modules like a crime scene every Tuesday.
I kept staring at those numbers and thinking: this shouldn't look like a rΓ©sumΓ©. It should look like a case file.
So I built Commit Crime Scene β a free, silly little tool that takes a GitHub username and stamps out a detective dossier: charges, a chaos score, a verdict class, and a downloadable PNG you can drop into Slack like evidence.
No login. No OAuth. No "connect your account so we can harvest your soul." Just a username and the public GitHub API.
The setup
You type a handle. The precinct goes to work.
Behind the yellow tape, the page:
Fetches the public user profile
Pulls recent public repos (up to 100)
Skims languages, forks, archive dust, follower ratios, account age
Invents a completely unserious legal case against you
Thirty seconds later you've got a paper-looking dossier: mugshot (your avatar), case ID, "charges," chaos score, languages of interest, and a rubber-stamp verdict that either says CASE CLOSED or β worse β STILL AT LARGE.
It's theater. Delightful theater. But it's theater powered by your actual public stats, so the jokes land a little too close to home.
Sample charges (yes, these are real outputs)
Depending on the profile, you might get hit with things like:
Operating with TypeScript, JavaScript, Python in broad daylight
Flooding the evidence locker with 87 public repos
Recruiting 240 witnesses (followers) β possible cult
No bio. Classic. Denies everything.
Suspected collaboration with non-human accomplices (looking at you, AI repo names)
If your bio contains TODO, WIP, hack, or broken⦠the tool notices. The statute of limitations does not.
Verdict classes (prepare your ego)
The classification system is not peer-reviewed. It is, however, emotionally accurate:
Serial Shipper β you open repos the way other people open tabs
PR Ghost β many eyes, few commits in the public square
Weekend Bandit β high chaos, midweek alibis thin
Dependency Hoarder β forks everywhere; originals unclear
AI Co-Conspirator β your bio/repos scream LLM energy
Cold Case Committer β years on the beat, suspiciously calm chaos score
Package Deal Felon β JS/TS/Python + elevated chaos = indictment
Suspect at Large β light paper trail; detective raises an eyebrow
There are a few more in the pool β Commit Scrawler, Branch Burglar, Merge Conflict Artist β because sometimes the algorithm just wants you roasted gently.
Chaos score: the fake science section
There's a 7β99 "chaos" number. It's not ML. It's not astrology. It's a cheeky blend of:
repos-per-year velocity
language variety
forks + archived repos
follower weight
whether you bothered to write a bio (no bio = slightly more suspicious, obviously)
Is it rigorous? Absolutely not.
Is it fun to compare with your teammates? Dangerously yes.
How it actually works (for the curious)
Stack-wise it's intentionally boring β in a good way:
Plain HTML / Tailwind / a little vanilla JS
GitHub REST API from the browser (/users/{login} + /users/{login}/repos)
Deterministic-ish hashing for case IDs and a couple of fallback verdicts
html2canvas to export the dossier as a PNG
Everything runs client-side. Your token never leaves your machine because⦠there is no token. Unauthenticated public API only.
Rate limits (the plot twist)
GitHub's unauthenticated rate limit is the one real villain in this story. If the precinct gets rate-limited (403/429), the tool doesn't die quietly β it offers a demo case so you can still screenshot, share, and keep the bit alive.
There's also a shareable URL shape (?u=yourhandle) so you can send someone a deep link and make them face their own verdict in public.
Why build a toy like this?
Because shipping doesn't have to be solemn.
Developers already live inside dashboards, CI red builds, and "just one more dependency." A weekend project that turns contribution graphs into noir stationery is a palate cleanser β and a surprisingly good conversation starter in Discord / team chats.
Also: if a tool makes someone laugh and click "download PNG," you've accidentally designed a viral loop. Yellow crime-scene tape helps.
Try it on yourself (and then on your manager)
Open Commit Crime Scene
Enter a GitHub username
Read the charges out loud for maximum courtroom energy
Download the PNG
Drop it in a channel with zero context
If you get Serial Shipper, wear it.
If you get PR Ghost, we both know what you did.
If you get AI Co-Conspirator, welcome to 2026.
π Investigate a profile: shipnative-landing.vercel.app/crime-scene
Built for fun under the ShipNative umbrella (an Expo / React Native AI starter kit + free setup checklist for people who actually want to ship apps). The crime scene tool is free, standalone, and not affiliated with GitHub β just a silly dossier generator for public profiles.
Now go file a case. The evidence locker is open.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.