SlopScore
00 crowd

VibeCemetery

Where vibe-coded projects rest in peace.
Open repo on GitHub Open the demogithub.com/azkian1/VibeCemetery
TypeScript · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 2 hours ago by azkian1 · last checked 53 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-16: Where vibe-coded projects rest in peace.; its own README says "Where vibe-coded projects rest in peace". 1 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as azkian1. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
Where vibe-coded projects rest in peace.
website
https://vibecemetery.app/
topics
cemeterygithubopen-sourcepixel-artvibe-coding
created
2026-03-18 · pushed 16 hours ago · 219 commits · 1 contributor
languages
TypeScript 90%JavaScript 8%CSS 1%PowerShell 0%Shell 0%
paperwork
contributinglicensereadme 71% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 2 hours ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
cssjavascriptpowershellshelltypescript
topic (detected)
cemeterygithubopen-sourcepixel-artvibe-coding
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: Where vibe-coded projects rest in peace.; its own README says "Where vibe-coded projects rest in peace". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

VibeCemetery

Dead projects should not disappear silently.

A pixel cemetery for abandoned GitHub repos and local projects.
No users. No runway. One very patient gravedigger.

Enter the cemetery · Bury a project · Agent instructions · Docs

Every unfinished idea deserves an ending

Half-built SaaS. A trading bot with one terrible trade. An MVP that never met a user. The folder called final-final-v3.

You spent time, tokens and a little hope on it. Give it a grave, an epitaph and a link people can visit. Keep the code. Let the project rest.

Scan your GitHub. Pick a cause of death. Begin the ritual. Close the tab. It is done.

The ritual

  • Bury it. Connect GitHub and pick an eligible abandoned repo. For local projects, give your coding agent the burial instructions.
  • Visit it. Walk the cemetery, read epitaphs and press F to pay respects.
  • Remember it. Share a grave. Find projects in The Crypt and their gravediggers in Necropolis.

GitHub repos must belong to you, contain a project, not be forks and have no pushes for at least seven days. Each account starts with four graves; sharing your first grave unlocks one more. GitHub and local projects use the same allowance. Burial never deletes your source code.

$GRAVE tributes

Voluntarily burn $GRAVE as a tribute to someone else's original, memorable project.

Open their grave, connect a wallet on Base and choose an amount. The tokens go to the burn address; the tribute is attached to that project's memorial after verification. The Crematory keeps the ledger.

A permanent gesture for a project that almost made it.

Tributes are optional: exploring the cemetery and burying a project require no tokens. Burns give no rewards or extra grave slots, and no tokens go to the project owner. GRAVE contract on Base.

A cemetery that grows

Two of nine zones are open, with 144 grave plots available in the current map. The full world is planned for 666 graves.

New zones will open at checkpoints tied to the amount of $GRAVE burned. Burn thresholds and zone releases will be announced as the world expands.

The nine-zone cemetery master plan

The master plan shows the full world concept. Its illustrated zone allocations are provisional; the playable map currently has 144 plots across two open zones.

A note from the Keeper

VibeCemetery is a solo indie project built with Claude Code, OpenCode and GPT.

After discovering AI coding, I spent two months making more than 50 projects: scripts, mini-games, experiments and half-alive ideas. Then the rush faded. I looked back and found a graveyard with no users and no future.

So I gave it a place.

Somewhere in this cemetery, an empty grave is already waiting for VibeCemetery itself. One day, the gravedigger will return with his shovel.

Even the cemetery must be buried.

Build with us

Next.js 16 · React 19 · Phaser 3 · Supabase Postgres · Base · Vercel

git clone https://github.com/azkian1/VibeCemetery.git
cd VibeCemetery
npm ci
cp .env.example .env.local
npm run dev

Configure your own development database and GitHub OAuth app using the setup guide. Start with Contributing and the map reference.

The v2 map, tiles and runtime images are committed here and served by the application CDN. Map loading does not use Supabase Storage.

You can reuse, modify and redistribute our map artwork, including in commercial projects, under the MIT license. Keep the license notice; see asset licensing.

Security · MIT code license


Built by @azaticus

"He buried others until it was his turn."

Read the rest on GitHub

Scan report · 2026-09-16
  • Prohibited terms or links
  • Repository eligibility
  • slopscore.md paperwork
  • Content policy
  • Risk review

0 comments

log in to comment.

report this listinglog in to report