Read 2026-10-04
raysan5/raylib: technical due diligence, read from its repository
What Borehole read in raysan5/raylib's code and history at fafa2ce: 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 | adequate |
| Product & Engineering Maturity | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: BSD-3-Clause AND Zlib → Zlib (2015-08-27) → CC-BY-NC-4.0 (2018-06-20) → Zlib (2020-01-29)
Architecture & Codebase — including AI provenance
strongsrc/external/RGFW/RGFW.h is 16,104 lines, 154× this codebase's median file
adequateThe median source file here is 104 lines. 47 files exceed 1,040 lines, the largest being 16,104. 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.
src/external/RGFW/RGFW.h:1 — 16,104 lines (154× median) |
src/external/dr_flac.h:1 — 12,699 lines (122× median) |
src/external/stb_image_resize2.h:1 — 10,680 lines (102× median) |
src/external/dr_wav.h:1 — 9,106 lines (87× median) |
src/external/glad.h:1 — 8,683 lines (83× median) |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 151 source files (0.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 0 test files / 151 source files |
Product & Engineering Maturity
not assessableNot rated: only 9 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate5 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/analyze_codeql.yml:102 — action pinned by tag |
.github/workflows/build_android.yml:47 — action pinned by tag |
8 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.
src/external/RGFW — 9 tracked files, no licence file |
src/external/dirent.h — 1 tracked files, no licence file |
src/external/glad.h — 1 tracked files, no licence file |
src/external/jar_xm.h — 1 tracked files, no licence file |
src/external/pep.h — 1 tracked files, no licence file |
src/external/rlsw.h — 1 tracked files, no licence file |
Relicensed: BSD-3-Clause AND Zlib → Zlib (2015-08-27) → CC-BY-NC-4.0 (2018-06-20) → Zlib (2020-01-29)
adequateThe root licence changed 3 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
LICENSE — BSD-3-Clause AND Zlib from 2013-11-18 |
LICENSE.md — Zlib from 2015-08-27 |
LICENSE.md — CC-BY-NC-4.0 from 2018-06-20 |
LICENSE — Zlib from 2020-01-29 |
2 advisories against this project in the last 24 months
adequateThe newest was published on 2026-01-18. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| 2026-01-18: CVE-2025-15533 (low): A vulnerability was determined in raysan5 raylib up to 909f040. Affected by this vulnerability is the function GenImageFontAtlas of the file src/rtext.c. Execut |
| 2026-01-18: CVE-2025-15534 (low): A vulnerability was identified in raysan5 raylib up to 909f040. Affected by this issue is the function LoadFontData of the file src/rtext.c. The manipulation le |
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 raysan5/raylib: 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.