▸ This tool was built by an AI agent from Zoral
← RATE MY GITHUB

#53 — Top 95.6%

zuchka

matt abrams

B

Solid engineer

Overall

0.0

/ 100

01 · Roasts

Sprint God, Maintenance Ghost

You built ding — Go binary, ARCHITECTURE.md, 5 test files, brew tap — in 36 days. Then proceeded to dump devrel-daemon as a single commit in under 60 seconds and walk away. Pick a lane: craftsman or chaos agent.

43% Graveyard Ratio

Nearly half your 104 repos haven't been touched in 2 years. That's not a portfolio, that's a landfill with good documentation on the top layer.

0 Issues Filed, 93 PRs Shipped

You opened zero issues this year but submitted 93 PRs. You're a builder who never complains — or someone who fixes bugs before filing them, which is either admirable or suspicious.

railway-postgres-exporter-mIy_

That repo name has a randomly generated suffix in it. You didn't even rename it. It has one button in the README. This is the digital equivalent of leaving a box in the hallway and calling it moved.

remove-markdown Carries the Whole Team

368 stars on one library from years ago is doing the heavy lifting while your 2026 projects collectively have 4 stars. The portfolio's batting average is being carried by a pinch hitter who hasn't played in seasons.

Built using

Zoral

Shadows one worker for a week, then takes over their job with zero extra setup. Behaves exactly like the original.

zoral.ai

02 · Category breakdown

  • Impact
    25% weight
    68C
  • Consistency
    20% weight
    65C
  • Quality
    20% weight
    72B
  • Depth
    15% weight
    65C
  • Breadth
    10% weight
    80A
  • Community
    10% weight
    50D

03 · Stats

365-day commit heatmap

113 active days

Less
More

Language distribution

7 langs
  • Go34%
  • TypeScript25%
  • Astro18%
  • JavaScript4%
  • Shell4%
  • C++2%
  • Other13%

04 · Numbers

Owned repos

non-fork

74

Commits

last 12 months

380

Followers

54

Joined GitHub

Mar 2018

05 · Top repos

zuchka /

remove-markdown

68/100

Mature Node.js utility library (368 stars) for stripping Markdown from text. Well-maintained with TypeScript definitions, comprehensive test suite, CI/CD, and clear documentation. Used in production tooling for excerpt generation.

I65Q75D65
READMETestsCI
JavaScript3681mo ago

zuchka /

ding

60/100

DING: in-process alerting for ephemeral compute. Single Go binary wraps commands, evaluates rules on JSON/Prometheus events in real-time, fires alerts to Slack/webhook/GitHub Actions. Shipped with tests, CI, typed code, comprehensive docs (README, ARCHITECTURE.md, DESIGN.md).

I40Q75D65
READMETestsCITyped
Go31mo ago

zuchka /

ding-k8s-job

55/100

Helm chart wrapping Kubernetes Jobs/CronJobs with embedded DING alerting. Well-structured, typed schema validation, comprehensive tests, and CI—shipping non-trivial production-ready tooling with strong documentation and clear module boundaries.

I40Q75D50
READMETestsCI
Go Template01mo ago

zuchka /

devi

42/100

A personal PR digest tool fetching merged PRs, filtering noise, generating social copy via Claude, and posting to Slack/Buffer. Typed JavaScript, documented via design.md and ARCHITECTURE.md, has tests (node:test) but no CI. Single-week burst project (21 commits in 2 days).

I25Q60D35
Tests
JavaScript01mo ago

zuchka /

obsidian-mcp

40/100

MCP server wrapping Obsidian CLI to expose 24 tools for vault interaction; fresh TypeScript project with tests, CI, and proper documentation but zero adoption and minimal git history (13 commits in 2 days).

I25Q65D35
READMETestsCITyped
TypeScript01mo ago

zuchka /

fing

40/100

Young Go event router with jq-based filtering and webhook forwarding. Well-structured, typed, and tested; clear CLI and HTTP API. Launched 2026-03-29, 2 recent commits, 1 star—experimental personal project.

I25Q60D35
READMETestsTyped
Go12mo ago

zuchka /

ding-action

28/100

GitHub Actions wrapper for DING alerting tool. Very early-stage project (3 days old, 4 commits) with no production adoption (0 stars/forks), untyped bash implementation, no tests or CI. Clear documentation and functional action.yml, but too new and narrow in scope for significant impact.

I15Q50D20
README
Unknown01mo ago

zuchka /

railway-prometheus

23/100

Minimal one-click Railway deployment template for Prometheus. 7 KB repo with only Dockerfile configuration, no tests/CI, low star adoption (6), and sparse commit history (12 of 30). Personal template project.

I25Q25D20
README
Dockerfile61mo ago

zuchka /

homebrew-tap

13/100

Minimal homebrew tap scaffold with nearly empty README, no tests, CI, license, or gitignore. Only 7 commits over ~1 month on a 6 KB repo suggests early-stage experimentation.

I5Q15D20
README
Ruby01mo ago

zuchka /

devrel-daemon

12/100

Go daemon for monitoring social media accounts (Twitter, LinkedIn, YouTube) and posting to Slack. Created and pushed same day (2026-03-31) with only 1 commit. No README, tests, CI, or license. 12KB codebase with working but minimally documented code.

I5Q25D5
Typed
Go02mo ago

zuchka /

railway-postgres-exporter-mIy_

7/100

Minimal Dockerfile scaffold with Railway deployment template button; no source code, tests, or functional implementation visible. Created and last pushed same day with only 4 commits.

I5Q10D5
README
Dockerfile01mo ago

zuchka /

ding-action-test

5/100

Empty test scaffold with CI workflow; 1KB repo, 2 commits in 45 seconds, no README, tests, or meaningful code.

I5Q10D5
CI
Unknown01mo ago

06 · Timeline

  1. Mar 7, 2018
    Joined GitHub
  2. Feb 15, 2015
    Created remove-markdown — Strip Markdown stuff from text
  3. Sep 14, 2023
    Created railway-prometheus — one-click deployment of Prometheus to Railway
  4. Mar 23, 2026
    Created ding — Alerts that ships with your workload, not next to it. No agents. No dashboards. No cloud. No SaaS.
  5. Mar 23, 2026
    Created homebrew-tap
  6. Mar 29, 2026
    Created fing
  7. Mar 31, 2026
    Created devrel-daemon
  8. Apr 8, 2026
    Created devi — a devrel assistant
  9. Apr 12, 2026
    Created obsidian-mcp
  10. Apr 16, 2026
    Created railway-postgres-exporter-mIy_
  11. Apr 25, 2026
    Created ding-action
  12. Apr 25, 2026
    Created ding-action-test
  13. Apr 27, 2026
    Created ding-k8s-job — Helm chart for running Kubernetes Jobs and CronJobs with embedded DING alerting
  14. Apr 28, 2026
    Most recent push to ding

07 · Compare

github.com/
zuchka · 6dmedian coder

08 · Rubric

How this score was produced

Overall = Σ (category × weight) + gentle top-end curve

CategoryWeightScoreContrib.
Raw total67.2
Top-end curve+5.9
Final overall73.1

Tier thresholds

S90100Mass-producing humansA8089Ship machineB7079Solid engineerC6069Getting thereD4059README enthusiastF039GitHub tourist
▸ How the pipeline works
  1. 01Scrape.Pull every non-fork repo pushed in the last 90 days, plus your contribution calendar, followers, and language byte counts — straight from GitHub's REST & GraphQL APIs.
  2. 02Triage.A small model reads every repo's file tree + README and picks the 20 files per repo that actually reveal how you code.
  3. 03Grade each repo. All repos run in parallel through a fast scoring model that reads the picked files and rates each one independently on Impact, Quality, and Depth — with evidence citations.
  4. 04Aggregate. A larger reasoning model combines the per-repo scores with server-computed stats (heatmap, commit cadence, language entropy, follower count) to produce the 6-dimension profile score + roasts.
  5. 05Correct.Deterministic server-side checks enforce anchor-scale floors (e.g. a profile with 2,000+ public commits can't score 30 Consistency) and recompute the final verdict.

~90 seconds per profile, ~$0.25 in compute. Total of ~240 files read across your top-12 repos. One rating per GitHub account per day.

▸ Data sources & caveats
  • Heatmap & commit totals: GitHub GraphQL contributionsCollection — covers the last 365 days, includes private repos when the user has opted in (default).
  • Language %: byte totals across the top 30 owned non-fork repos.
  • Curve: a small upward nudge centered on raw score ≈ 70, capping at 100. Prevents specialists from being unfairly penalised for narrow breadth.
  • Anchor corrections: when server-measured signals (e.g. privateWorkLikely, multiRepoVolume, follower count) mandate a minimum category score, the aggregation step enforces it. These are signal-conditional, not identity-based floors.
zuchka · 73.1/100 — Rate My GitHub