Borehole · Project · free tier
ppy/osu
Free reading: not for reliance
257761d · 50,000 commits · 5,583 files
Read 2026-10-04

ppy/osu: technical due diligence, read from its repository

What Borehole read in ppy/osu's code and history at 257761d: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

osu.Game/OsuGame.cs is 1,843 lines, 24× this codebase's median file

adequate

The median source file here is 74 lines. 9 files exceed 1,000 lines, the largest being 1,843. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.

Evidence
osu.Game/OsuGame.cs:1 — 1,843 lines (24× median)
osu.Game/Screens/Edit/Editor.cs:1 — 1,689 lines (22× median)
osu.Game/Database/RealmAccess.cs:1 — 1,533 lines (20× median)
osu.Game/Screens/Play/Player.cs:1 — 1,322 lines (17× median)
osu.Game/Screens/Select/SongSelect.cs:1 — 1,296 lines (17× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

strong
05.27

The build runs third-party code it does not pin

adequate

4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.

Evidence
.github/workflows/ci.yml:53 — action pinned by tag
.github/workflows/ci.yml:132 — action pinned by tag
05.26

1 locked dependency has published vulnerabilities, 1 high or critical

adequate

1 of 32 locked dependencies match 1 published advisories in OSV, 1 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. None of the high or critical ones is in what the product ships: the project marks 1 as not affecting it, with its reason beside the reference.

Evidence
osu.Game/osu.Game.csproj — AutoMapper 13.0.1: GHSA-rvv3-g6hj-g44x (high), fixed in 16.1.1; the project marks it as not affecting it, which is a question to ask

Observability & Operations

not assessable

Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on ppy/osu: every dimension, the questions for the room, and the audit log.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.