SlopScore
00 crowd

rings

Tree rings for Git repos: one ring per month, coloured where the history discloses AI co-authors, agent accounts or bots. Agent skill + CLI, no keys.
Open repo on GitHub Open the demogithub.com/vnmoorthy/rings
JavaScript · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)devtools🤖 claude-code🤖 codex
listed 2 hours ago by vnmoorthy · last checked 2 hours 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-10-18: Tree rings for Git repos: one ring per month, coloured where the history discloses AI co-authors, agent accoun; its own README says "com , Assisted-by: Codex , AI-assisted , Generated with Claude Code ; Copilot, Cursor, Gemini, Aider, opencode, Amp". 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 vnmoorthy. 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
Tree rings for Git repos: one ring per month, coloured where the history discloses AI co-authors, agent accounts or bots. Agent skill + CLI, no keys.
website
https://vnmoorthy.github.io/rings/
topics
agent-skillaiclaude-codecodexdeveloper-toolsgitgit-historyvisualization
created
2026-10-17 · pushed 6 hours ago · 3 commits · 1 contributor
languages
JavaScript 100%
paperwork
licensereadme 42% 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
devtools
ai_generated
mostly
human_touch
light
status
works-on-my-machine
built_with
claude-codecodex
language (detected)
javascript
topic (detected)
agent-skillaiclaude-codecodexdeveloper-toolsgitgit-historyvisualization
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: Tree rings for Git repos: one ring per month, coloured where the history discloses AI co-authors, agent accoun; its own README says "com , Assisted-by: Codex , AI-assisted , Generated with Claude Code ; Copilot, Cursor, Gemini, Aider, opencode, Amp". 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

oven-sh/bun drawn as tree rings: monthly rings grow from 2021; orange arcs show commits with Claude co-author trailers in 2025 and early 2026, teal arcs show commits by bot-named accounts

Rings

Tree rings for your codebase: see when AI shows up in git.
One ring per month since the first commit. Colour wherever the history itself discloses an AI co-author, an AI agent's own account, or a bot-named account.

Gallery of famous repos · Install · How it reads history · 中文

npx skills add vnmoorthy/rings -g      # then, in Claude Code or Codex: /rings
npx github:vnmoorthy/rings oven-sh/bun # or any owner/name, URL, or local path

No API keys, no dependencies (Node built-ins only), nothing uploaded. Remote repos are cloned history-only, so even large ones take seconds.

What it shows

Rings cuts a repository open like a log. The pith is the first commit, the bark is today. Each ring is one month (one week, day or commit for younger repos) and its width comes from that month's commit count. Coloured arcs inside a ring show the share of that month's commits that carry a signal:

Signal Example
🟧 AI co-author / assisted-by trailer Co-authored-by: Claude <noreply@anthropic.com>, Assisted-by: Codex, AI-assisted, Generated with [Claude Code]; Copilot, Cursor, Gemini, Aider, opencode, Amp ...
🟪 AI agent account the author is copilot-swe-agent[bot], devin-ai-integration[bot], google-labs-jules[bot], claude[bot] ...
🟦 Bot-named account dependabot[bot], GitHub Actions, TypeScript Bot, *-bot, robobun@oven.sh, and chores pushed by an agent's account ...
🟩 During an agent session (your own repo, opt-in) made while a local Claude Code or Codex session was running in that repo
🪵 No AI signal not the same as "written by a human"

Hover a ring for its counts, agents, accounts and a sample commit hash. Export a 1080×1080 PNG or a 1200×630 social card from the page.

From the gallery

Numbers from each project's public history (non-merge commits on the default branch), read on 17 Oct 2026:

  • microsoft/vscode: commits with an AI co-author trailer (almost all GitHub Copilot) went from 5% in Jan 2026 to 68% in Sep 2026.
  • nodejs/node: commits with an Assisted-by line naming an AI tool (mostly opencode and Codex) rose from 11% in Jul 2026 to 36% in Sep 2026.
  • neovim/neovim: 24% of September 2026's commits end with a plain AI-assisted line.
  • oven-sh/bun: Claude co-author trailers peaked at 62% of commits in Feb 2026, while monthly commits grew from 175 in Mar to 1,042 in Aug 2026.
  • Aider-AI/aider: aider's own repo, where aider-marked authors peaked at 62% of commits in Mar 2025.

Disclosure is not usage. Trailers change with tool defaults, squash merges and agents that commit under their own accounts. Rings shows what the history says and nothing more. See all repos →

Install

As an Agent Skill (a folder with a SKILL.md; this repository is that folder):

Agent Command
Claude Code npx skills add vnmoorthy/rings -g -a claude-code
Codex npx skills add vnmoorthy/rings -g -a codex
OpenCode npx skills add vnmoorthy/rings -g -a opencode
anything else git clone https://github.com/vnmoorthy/rings and point your agent at SKILL.md

Then ask: "ring this repo", "draw tree rings for vercel/next.js", or /rings.

As a plain CLI:

npx github:vnmoorthy/rings [repo] [options]

  repo              local path (default .), owner/name, or a GitHub URL
  -o, --out <file>  HTML to write (default ./<owner>-<name>-rings.html)
  --sessions        your own repo: mark commits made during local Claude Code / Codex sessions
  --unit <u>        auto | month | quarter | week | day | commit
  --bots a,b        extra automation accounts      --humans a,b   never count these as bots
  --ref <ref>       branch to read                 --json         machine-readable summary
  --open            open the page when done

How it reads history

  • git log --no-merges on the default branch, author dates in UTC. Only commit metadata is read; remote repos are cloned with --filter=tree:0 into ~/.cache/rings.
  • Trailers. A Co-authored-by line counts when it names a coding agent by its own display name or no-reply address (Claude <noreply@anthropic.com>, Cursor Agent <cursoragent@cursor.com>, copilot-swe-agent[bot] ...). Company domains are never enough (Bun's engineers commit from anthropic.com, OpenAI's from openai.com), and a person's full name such as "Claude Paroz" or "Devin Weaver" is never counted; a co-author whose name is only "Claude", "Cursor" or "Gemini" counts as the tool unless the address is a personal mailbox. Assisted-by, AI-assisted, Generated-by and Generated with [tool] lines count when they name a tool or model (claude:opus-5.5, Codex, openai:gpt-5.5, or just AI). Lines that GitHub squash merges push out of git's trailer block are read too. The rules and their tests are in lib/classify.mjs and test/.
  • Ring size adapts to age: monthly for repos older than two years, weekly from three months, daily from a week, one ring per commit below that. Width is the square root of the commit count, capped at 2.5× the median so one burst cannot flatten the rest; empty months leave a thin dark line. A commit whose author date is more than a year away from its commit date and isolated from the rest (a wrong clock) is set aside and reported, never one that discloses AI.
  • --sessions reads only the first and last 64 KB of each transcript in ~/.claude/projects and ~/.codex/sessions (working directory and timestamps) and marks commits made during a session or within 10 minutes of it. It never leaves your machine, and transcripts your tools have already cleaned up simply aren't there.

Maintainers: if you'd like your repo out of the gallery or a bot list corrected, open an issue.

Prior art

Gource animates repository history as a tree of files. git-of-theseus charts how much code from each year survives. git-ai tracks AI authorship line by line as you work. Rings is a single still picture of a repo's whole life, built only from what its commits already disclose.

中文

Rings:把代码仓库像树干一样切开,看提交记录里 AI 是什么时候出现的。 从第一次提交开始,每个月一圈年轮(较新的仓库按周、按天或按提交),宽度由当期提交数决定。如果提交带有指名 AI 编程工具的 trailer(如 Co-authored-by: Claude <noreply@anthropic.com>、Assisted-by: Codex),或提交作者是 AI 代理自己的账号(如 copilot-swe-agent[bot]),或作者名看起来是机器人账号,就按这些提交在当月的占比给年轮着色。提交记录里的标注不等于实际使用:工具默认设置、squash 合并、代理用自己的账号提交,都会让标注出现或消失。没有颜色只代表“没有信号”,不等于“人写的”。

npx skills add vnmoorthy/rings -g     # 然后在 Claude Code / Codex 里输入 /rings
npx github:vnmoorthy/rings oven-sh/bun

无需 API key,零依赖,不上传任何数据。查看知名仓库的年轮 →

License

MIT

Read the rest on GitHub

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

0 comments

log in to comment.

report this listing — log in to report