Open-source Eurorack modules

a reference table of buildable DIY modules, every cell traced to a file in its repo

About

1021 buildable open-source Eurorack modules from 333 GitHub repositories by 240 makers. The table behind this site is data/modules.tsv in daaaaaaaaaniel/my-awesome-eurorack; the site is regenerated from it and adds nothing.

What the fields mean

Type
The raw type string from the repo, plus tags from data/type-categories.tsv (multi-function modules get several). Tags marked draft are keyword-rule proposals awaiting review.
Maker
As recorded in the repo. A clone or port is credited "Original + Porter" (e.g. "Mutable Instruments + Sluisbrinkie"); the Maker filter lists each name separately, so the module appears under both. Spelling variants of one maker are folded together by data/maker-aliases.tsv; the credit line keeps the repo's spelling.
Mounting
SMD, THT or both, read from the board files' footprints or from a statement in the repo. Blank means neither was available in scope — it is not a guess. "Component confidence" says which: Strong (footprints counted), Stated (repo says so in text), Weak, Deferred (no machine-readable board file or BOM found).
Board parts
Part counts: footprints from the board files (component confidence Strong, 606 modules) or parts from a machine-readable BOM (Stated, 78 modules, marked "counted from the BOM"). Another 60 modules have a tally from incomplete evidence (Weak / Deferred); it is not shown, and the module page says so rather than claiming there is nothing to count. The number includes panel parts (jacks, pots, switches, LEDs, headers; not mounting holes) where the detector recorded a panel count; elsewhere it is board parts only, and the module page and the tooltip say which. This number never feeds the THT / SMD / both call, which ignores panel hardware. A * after the number means the folder held several board files and the detector summed them, so alternate versions may be pooled (the module page says how many). Pin counts are not recorded.
HP
Panel width. Measured from the panel outline when it is 3U (127.5–129.5 mm) or 1U high and the width is a whole number of HP (5.08 mm each, minus up to 1 mm); otherwise stated in a panel file name or the README. ? = panel files exist but no width could be settled (no measurable outline, or measured and stated disagree). The module page says which.
Panel files
The panel's source files: KiCad, Eagle, EasyEDA, gerbers, SVG, DXF, Illustrator, PDF, Front Panel Designer or 3D (STL/STEP/…). Photos of a panel don't count. "Only modules with panel source files" keeps the modules that have any.
Photos, Build guide
Links to photos and renders in the module's folder, and to build/assembly documents or a folder of build-step photos. Schematics, diagrams and screenshots are left out.
Files in repo
Which design files exist: a schematic (linked when it's a single PDF), KiCad / Eagle / other layout sources, gerbers, a machine-readable BOM.
License
The raw statement is kept as recorded. On top of it, data/license-map.tsv splits each statement into grants — a module can carry one license for hardware and another for firmware — each with a version-free family (filterable by ?lic= in the URL) and a terms class that describes the license family, never the module (the License terms filter). Versions are shown only when the repo states one. A blank cell means no license found in the files checked, which is not the same as the repo saying there is none. Rules in data/licenses.md.
Build status
prototype when the repo clearly labels the build untested or in progress; prototype? when the wording is ambiguous. Never inferred from a version number.
Evidence
Each module page quotes the file path or README line every non-blank cell came from.

Rules the data follows

Modelled loosely on signalfunctionset.com/builds, whose catalogue is curated by hand; this one is extracted from the repos and shows its working.