Read 2026-10-04
godotengine/godot: technical due diligence, read from its repository
What Borehole read in godotengine/godot's code and history at 4617300: 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.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.github/PULL_REQUEST_TEMPLATE.md:7: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongdrivers/alsa/asound-so_wrap.c is 14,005 lines, 100× this codebase's median file
adequateThe median source file here is 139 lines. 245 files exceed 1,390 lines, the largest being 14,005. 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.
drivers/alsa/asound-so_wrap.c:1 — 14,005 lines (100× median) |
servers/rendering/shader_language.cpp:1 — 12,329 lines (88× median) |
servers/rendering/rendering_device.cpp:1 — 10,542 lines (75× median) |
scene/gui/text_edit.cpp:1 — 10,162 lines (73× median) |
editor/animation/animation_track_editor.cpp:1 — 10,057 lines (72× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate4% of bug fixes add or change a test
adequateOf 3180 fixes in the last 24 months, 138 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 138 of 3180 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate6 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.
.github/workflows/android_builds.yml:157 — action pinned by tag |
.github/workflows/android_builds.yml:163 — action pinned by tag |
5 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
modules/mono/thirdparty/libSystem.Security.Cryptography.Native.Android.jar — 1 tracked files, no licence file |
modules/mono/thirdparty/libSystem.Security.Cryptography.Native.Android.jar.source.txt — 1 tracked files, no licence file |
modules/mono/thirdparty/mono_delegates.h — 1 tracked files, no licence file |
modules/mono/thirdparty/mono_types.h — 1 tracked files, no licence file |
thirdparty/linuxbsd_headers — 143 tracked files, no licence file |
Observability & Operations
not assessableNot rated: only 4 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on godotengine/godot: 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.