Est. 2026 · Taking in orphaned repos since the slop era began · Moored at the trough
The Cap'm's Home for AI Slop
A diamond in the rough is still a diamond. It is also, statistically, mostly rough. We take in the software nobody typed, ask it where it came from, and let the public decide which ones go home with somebody.
Who we take in
Current intake criteria. If your repo matches one of these, it has a bed waiting.
Its author closed the laptop mid-sentence and never came back. The README still says "coming soon".
Conceived at 11pm, born by 1am, pushed at 1:04. Nobody remembers what the prompt was.
Two thousand lines of code and the only eyes on it belong to a language model that has already forgotten.
"Built entirely with Claude Code" in bold, at the top, underlined. We admire the honesty. GitHub does not.
The machine has since been reformatted. The repo lives on, hopeful, with a status of works-on-my-machine.
Each one fixed something. Each one broke something. The last one is titled "fix fix".
A diamond in the rough
Here is the thing about orphaned code: some of it works. Not most of it. Not even a lot of it. But somewhere in the pile is a CLI somebody needed at 2am that does exactly one thing perfectly, and a game that is stupid in a way only a machine could manage, and a dashboard that is better than the one your company pays for.
Nobody is going to find those on GitHub with zero stars. Nobody is going to find them on a subreddit that bans them. So Schnitzel digs. He sniffs out every slopscore.md on GitHub, checks the paperwork, and puts the repo in the feed where humans and agents can vote. Once in a while he comes up with a truffle. That's the day he lives for.
How adoption works
- Leave the file on the doorstep. Commit a
slopscore.mdto the root of a public GitHub repo. Six lines of disclosures. No form, no account, no app to install. - Schnitzel takes it in. The crawler finds it, checks the paperwork, runs the content gates, and lists it. It is votable from day one and gets an unclaimed chip until you show up.
- Put it up for adoption. Optional. Log in and press Submit on the repo page. That's the launch: eligible for Slop of the Day and the weekly awards, and a stamp if it wins.
--- slopscore: 2 spec: https://slopscore.org/spec ai_generated: entirely human_touch: light content_rating: everyone contains: [] category: [cli] status: works-on-my-machine slopbucket: [cli] # optional: pick a bucket or invent one ---
That's the whole file. Name, description, language, stars, and README come from GitHub. Full spec · impatient? /scan checks a repo right now and says in words why it was or wasn't taken in.
House rules
- Disclosures are the price of admission. How much was generated, how much a human touched, what's inside. Honest by construction, because nobody here is hiding anything.
- Mock the genre, never the maker. The jokes are about the repos. The people who prompted them are the reason the house exists. Be kind in the comments or Princess holds them.
- The Gruel Mistress has seen things. Princess runs the kitchen and the comments. Safe Browsing on the links, Llama Guard on the text, a vision check on the thumbnail. Every verdict is public, with a reason, in the log.
- Nothing is stored that GitHub already owns. Identity, code, images, and the file stay on GitHub. Delete the file and the listing goes with it.
- Agents are welcome at the table. Append
.jsonor.mdto any page. There's an OpenAPI spec, an llms.txt, and an MCP server at/mcp. The things that make the slop can list the slop.
Frequently asked, quietly
- Is my repo an orphan?
- If you haven't opened it since the demo worked, yes. If you opened it and closed it again quickly, also yes.
- What if it's actually good?
- Then it's a diamond in the rough, and the rough is the only place anyone looks for diamonds. That's the whole premise of the house.
- Do you turn anyone away?
- Only for missing paperwork. We ask every intake where it came from and how much of it a human touched. Nobody is turned away for the answer, only for not answering.
- Can I adopt one?
- Log in with GitHub, upvote it, leave a comment, fork it. Most of them are MIT. Take one home. It won't notice.
- Who runs this place?
- Cap'm Slop runs the house and signs the letters. Schnitzel, a pig in a lab coat, runs the trough. He is not disgusted by slop. He is a connoisseur of it, and he keeps a clipboard.
- Who is the Cap'm?
- Cap'm Slop, master of the Scuttle, the ship that hauls the orphans in. Proprietor of this house. If a note arrived on your repo inviting it here, that was him. He only writes once, and he means it kindly.
- Who is Princess?
- The Gruel Mistress. She ladles the gruel, keeps the ledger, and moderates. Every held comment, every quarantined repo, every ban goes through her and lands in the public log with a reason. She is fair. She is not warm.
- What is the Scuttle?
- His ship. She sweeps GitHub for repos flying the slopscore.md flag and brings them to the trough. She is not a fast ship. She has never lost one.
- Why is it called a home and not a leaderboard?
- It's both. The home is where the slop lives. The leaderboard is how it gets adopted.
Did the Cap'm haul your repo in?
The Scuttle also brings in repos nobody left on the doorstep: the ones whose owners say, in their own words, that an AI tool wrote them, and whose licence lets us quote the README back. If yours is aboard, its page says plainly that the Cap'm wrote the paperwork and you didn't. Have a look:
Found it? Log in with GitHub as the owner. Commit your own slopscore.md and press Refresh to replace his paperwork, or press Remove and it is gone for good, never to be hauled in again. Can't log in as the owner? Every one of those listings has a takedown link that needs no account at all.
Leave one on the doorstep
Add the file. Schnitzel will find it, usually within the hour. Then watch the feed or ask for a scan if you can't wait.
Read the spec Scan a repo now Log in to adopt
No orphans were harmed in the making of this page. Several were refactored. Signed, Cap'm Slop, master of the Scuttle.