Borehole · Project · free tier
neutrinolabs/xrdp
Free reading: not for reliance
5e7decc · 5,420 commits · 719 files
Read 2026-11-03

neutrinolabs/xrdp: technical due diligence, read from its repository

What Borehole read in neutrinolabs/xrdp's code and history at 5e7decc: 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 Maturityadequate
Security & Reliability Posturenot assessable
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed
  • COPYING: Relicensed: GPL-2.0 → GPL-with-exception (2006-11-14) → Apache-2.0 (2012-09-20)
  • .gitmodules:1: 2 submodule(s) this survey does not read: librfxcodec, libpainter

Architecture & Codebase — including AI provenance

strong
01.6

xrdp/xrdp_mm.c is 5,651 lines, 31× this codebase's median file

adequate

The median source file here is 177 lines. 18 files exceed 1,770 lines, the largest being 5,651. 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
xrdp/xrdp_mm.c:1 — 5,651 lines (31× median)
common/os_calls.c:1 — 4,666 lines (26× median)
xrdp_accel_assist/encoder_headers/nvEncodeAPI_11_1.h:1 — 3,907 lines (22× median)
xrdp_accel_assist/encoder_headers/nvEncodeAPI_11_0.h:1 — 3,844 lines (21× median)
libxrdp/xrdp_orders.c:1 — 3,188 lines (18× median)

Engineering Process & SDLC Maturity

strong
02.6

Almost no process scaffolding exists in the repository

adequate

Of five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.

Evidence
1 of 5 markers present across 719 tracked files

Product & Engineering Maturity

adequate
04.19

10% of bug fixes add or change a test

adequate

Of 60 fixes in the last 24 months, 6 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.

Evidence
6 of 60
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v0.10.6, is not on the branch this survey read; the newest release on it is v0.9.18. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v0.10.6

Security & Reliability Posture

not assessable
05.9

1 vendored component with no licence

adequate

Third-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.

Evidence
third_party/COPYING-THIRD-PARTY — 1 tracked files, no licence file
05.60

Relicensed: GPL-2.0 → GPL-with-exception (2006-11-14) → Apache-2.0 (2012-09-20)

adequate

The root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

Evidence
COPYING — GPL-2.0 from 2004-07-09
COPYING — GPL-with-exception from 2006-11-14
COPYING — Apache-2.0 from 2012-09-20
05.65

19 advisories against this project in the last 24 months, 12 high or critical

adequate

The newest was published on 2026-07-02. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 18 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.9.18. Answer lives in: the release you run, set against each fixed version. GHSA-rwvg-gp87-gh6f (critical) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 4 records name xrdp with nothing tying them to this repository (CVE-2008-5902, CVE-2008-5903, CVE-2008-5904, …).

Evidence
2026-07-02: GHSA-6g36-mxcf-r3gc (moderate), fixed in 0.10.6.1: Improper Input Validation in xrdp MCS Data Processing Leading to Potential Information Leak
2026-07-02: GHSA-3m4m-h22g-c7xx (moderate), fixed in 0.10.6.1: Out-of-Bounds Read in xrdp Client Control PDU Processing
2026-07-02: GHSA-9j3q-9mvw-qv7j (high), fixed in 0.10.6.1: Infinite loop denial-of-service vulnerability in xrdp during RDP packet processing
2026-07-02: GHSA-hh7r-2rmq-q4g4 (high), fixed in 0.10.6.1: Heap-based Buffer Overflow in xrdp Virtual Channel Forwarding
2026-07-02: GHSA-v8w6-pf78-9458 (high), fixed in 0.10.6.1: Integer Overflow leading to Out-of-bounds Read in xrdp vnc-any mode

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on neutrinolabs/xrdp: 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.