slopify

Grade a GitHub repo with the slop formulas, not a vibe score.

Verbosity and erosion as published. ΔLOC from GitHub weekly stats, shown separately. A username writes a SKILL.md from recurring hits across recent public repos. No account.

Two published formulas.

Method

Published formulas, stated approximations.

slopify scores a public snapshot. It does not ask a model how “sloppy” the code feels. The two structural metrics come from SlopCodeBench2 and were restated by Earendil1. The letter grade is slopify’s own scale on top of those two numbers.

  1. Verbosity

    Share of source lines that are either a wasteful-code hit or part of a duplicated window. SlopCodeBench uses 137 ast-grep8 rules plus clone lines. We do not have that rule set. Flagged lines here are a smaller, listed set of patterns (, comparisons to True/False, json.dumps/loads round-trips, swallowed except/catch, and similar). Clone lines are 6-line token-normalized windows6.

  2. Mass and erosion

    How much of the codebase’s complexity mass sits in functions above McCabe’s limit of 1034. SlopCodeBench chose that cutoff from Radon rank C5. Cyclomatic complexity on a connected control-flow graph is ; here is 1 plus decision keywords, boolean operators, and ternaries — a static count, not a graph walk.

  3. ΔLOC

    Earendil’s simplest slop signal: change in line count1. We read GitHub’s weekly code-frequency series7. Shown next to the grade, never mixed into it. Missing when GitHub returns 202 or an empty series.

  4. Letter grade

    and are Earendil’s published human and agent means. Letters: if , if , if , if , else . The letter is that average, so a quiet verbosity score can hide agent-range erosion (or the reverse). The report names which metric pulled the letter. This mapping is slopify’s, not a result from the paper.

Means used on this site vs SlopCodeBench Table 2 (later, larger panel).
Source human agent human agent
Earendil (grade)1
SCBench Table 22

Limits