All projects MercuryPitchRepo Report
Overturerepoas ofmain

MercuryPitch

A free practice studio in the browser that hears every note you sing or play.

MercuryPitch listens through the microphone while you practise: vocal pitch training, vocal range tests, karaoke with live scoring, and guitar, piano and drum rooms that show every note you hit. It runs in the browser and ships to iOS and Android inside native shells. This page plays its repository back as a score.

♪ Start with the showstoppers 𝄞 The staff behind the title vibrates with each week's commit volume, left to right
Liner notesThe headline numberstutti

The Whole Programme in Six Numbers

Share card1200 × 630 for link previewsthe album cover

The Album Cover

The whole report as one image, sized for link previews on Open Graph, X, LinkedIn and Slack. The copy and download buttons export exactly this frame at 2400 × 1260. The record's grooves are the top-level folders, banded by file count.

✦
Bravissimo: the moments that make the audience gasp

Showstoppers

Outliers, oddities and records pulled from the data by rule, not by hand: each ticket prints only when a statistic crosses a threshold for unusual, so every repository earns its own surprises.

Fig.Wow factsfortissimo

Tickets to the Surprising Parts

Every stub is admit-one: the figures below show where each number comes from.

I
Andante: at a walking pace

Instrumentation · lines of code

cloc counts every tracked text file. Code is split into three instrument families: strings (general code), woodwinds (CSS, HTML and other markup) and brass (the native Swift and Java of the iOS and Android shells). Data and docs sit backstage, counted but kept apart.

Fig.Lines of code by familytutti

The Orchestra

A seating chart where every chair is a fixed number of lines of code. Sections sit left to right; each language takes the chairs it has earned.

Fig.Lines of code by languagea mixing desk, in decibels

The Mixing Desk

One channel strip per language. Faders sit on a logarithmic scale, the way audio engineers read loudness, so the smallest language and the largest share the same desk.

Fig.Tests vs app codeprova

Rehearsal vs Performance

General code split by path: tests/, e2e/, *.test.*, *.spec.* and Playwright test folders are rehearsal; the rest is the performance.

Fig.Native app codepianissimo

The Brass Section

Native sources of the iOS and Android shells, with each shell's build files and resources listed alongside.

II
Allegro vivace: fast and lively

Tempo · commits

Every commit reachable from the main branch, read from a fresh clone and checked against the GitHub API. Every time is moved into one zone, so commits stamped by UTC servers don't fake a night shift.

Fig.Commits per daythe waveform

The History as One Waveform

Each bar is a day of commits, mirrored like an audio file.

Fig.Commits by day × hourpiano roll

The Piano Roll

The 24 hours of the day map onto exactly two octaves of keys, from C3 at midnight up to B4 at 23:00. Each note is one hour of one day, and its brightness is how many commits landed in it, like velocity in a DAW.

Fig.Weekday × hourstep sequencer

The Weekly Groove

A drum-machine grid: seven tracks (days) and 24 steps (hours). The brighter the pad, the more commits fell on that beat.

Fig.Pace & streaksmetronome

The Metronome

Tempo written the way a score writes it: one beat per commit, per active day.

Fig.Where the work was playedfretboard

The Fretboard

Six strings for the six most-touched top-level folders, one fret per week. A finger dot shows how many commits touched that folder that week; the busier a folder overall, the heavier its string.

Fig.Lines over timecrescendo

Crescendo

The codebase rebuilt from the diff of every commit on the main branch: git numstat along the first-parent chain, with blanks and comments included and excluded files left out.

Fig.Who wrote the commitsliner-note credits

Credits

Authors merged by e-mail, name and GitHub login, then credited the way an album sleeve would.

III
Moderato: every pull request, engraved

Score · pull requests

Counts come from GitHub search. Per-PR timestamps come from the GitHub REST API, pinned to the same snapshot, so every total can be checked against the counts.

Fig.All pull requestspartitura, 7/4

The Pull Request Score

Every PR is a note, written in the order PRs were opened. One bar is one week and 7/4 means one beat per day. The faster a PR merged, the higher and shorter its note. Press play to hear it.

Fig.PR outcomescadence

Resolution

How each pull request's phrase ended: resolved (merged), left unresolved (closed) or still suspended (open).

Fig.Time to mergenote values

The Rhythm of Review

Merged PRs grouped by how long they waited, written as note values from sixteenth (≤ 15 minutes) to whole note (more than a week).

Fig.PRs per weekspectrum analyser

Weekly Cadence

LED columns show PRs merged each week; the floating peak-hold bar marks PRs opened that week.

IV
Dolce: softly, sweetly

Applause · stars & community

Stars, forks and watchers from the GitHub API at the snapshot, with the date of every star.

Fig.Stars over timestanding ovation

Standing Ovation

Cumulative stars, day by day, from the repository's creation to the snapshot.

V
Maestoso: with majesty

Arrangement · files & folders

The tracked tree at HEAD: git ls-tree for files and folders, git ls-files --eol to separate binary from text, and Git LFS pointer files parsed for their true size.

Fig.Folder tree by file count33⅓ rpm

The Repo on Vinyl

A sunburst pressed into a record. The inner groove holds top-level folders, the outer grooves hold the sub-folders, and arc length is file count. Hover to stop the platter.

Fig.File typesside A / side B

The Tracklist

The most common file extensions, ranked by number of files. Badges flag binary files and files stored through Git LFS.

Fig.Lines by folderdrum pads

The Drum Pads

A squarified treemap laid out as performance pads. Each pad's area is its lines of code, its glow is the family that dominates it, and the LED strip along its foot shows the full mix. Switch to “Everything” to let the data in.

Fig.Files by folder deptha descending scale

How Deep the Tree Goes

Files counted by how many folders down they sit, drawn as a scale of notes.

Fig.Biggest files & foldersfortissimo

The Heaviest Instruments

The largest files in git and the folders that hold the most files directly.

VI
Attesa: the house lights come up

The Audience · product users

Repository statistics can't see the people who practise with MercuryPitch. These numbers come from the product's own database and web analytics, exported as aggregate counts only.

Fig.Usersthe house

Who Is in the Hall

Registered users, active listeners and growth over time.

§
Programme notes: how this was measured

Sources, definitions & caveats