Read 2026-10-28
duendesoftware/products: technical due diligence, read from its repository
What Borehole read in duendesoftware/products's code and history at 222118c: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongidentity-server/src/IdentityServer/Internal/Saml/Sp/Metadata/MetadataSerializer.cs is 5,202 lines, 100× this codebase's median file
adequateThe median source file here is 52 lines. 11 files exceed 1,000 lines, the largest being 5,202. 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.
identity-server/src/IdentityServer/Internal/Saml/Sp/Metadata/MetadataSerializer.cs:1 — 5,202 lines (100× median) |
storage/src/Storage.Oracle/Internal/OracleStorageEngine.cs:1 — 2,873 lines (55× median) |
storage/src/Storage.MsSql/Internal/MsSqlStorageEngine.cs:1 — 2,842 lines (54× median) |
storage/src/Storage.PostgreSql/Internal/PostgreSqlStorageEngine.cs:1 — 2,624 lines (50× median) |
storage/src/Storage.Sqlite/Internal/SqliteStorageEngine.cs:1 — 2,522 lines (48× median) |
Engineering Process & SDLC Maturity
adequate5% of recent commits change more than 2,000 lines
adequate57 of 1140 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 57 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 5,719 tracked files; 0 present |
6 locked dependencies have published vulnerabilities, 17 high or critical in what ships
adequate6 of 271 locked dependencies match 18 published advisories in OSV, 17 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.
bff/templates/src/BffBlazorAutoRenderMode/BffBlazorAutoRenderMode/BffBlazorAutoRenderMode.csproj — Microsoft.AspNetCore.Components.WebAssembly.Server 10.0.0: GHSA-g27p-qf6j-c96c (high), fixed in 10.0.13 |
Directory.Packages.props — Microsoft.AspNetCore.Components.WebAssembly.Server 10.0.4: GHSA-g27p-qf6j-c96c (high), fixed in 10.0.13 |
bff/Directory.Packages.props — Microsoft.AspNetCore.Components.WebAssembly.Server 10.0.7: GHSA-g27p-qf6j-c96c (high), fixed in 10.0.13 |
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 5 lines, unrecognised |
4 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-10-07. 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 4 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: its keyword search for 'products' is too broad to read whole (9,125 records); NVD: 298 records name products with nothing tying them to this repository (CVE-2010-2371, CVE-2010-2372, CVE-2010-2414, …).
| 2026-10-07: GHSA-vvg7-p7jw-8qr3 (moderate), fixed in 2.2.1: BFF session cookie forwarded to remote APIs proxied through YARP |
| 2026-10-07: GHSA-4j63-5v5f-xcc4 (moderate), fixed in 4.0.4: Dynamic-frontend remote API proxy (WithRemoteApis) skips the BFF anti-forgery header |
| 2026-09-28: GHSA-mxv6-xwqj-ww2p (high), fixed in 7.0.10: Insufficient validation of pushed authorization requests in IdentityServer |
| 2024-10-28: GHSA-v9xq-2mvm-x8xc (low), fixed in 7.0.8: Insufficient validation of DPoP cnf claim in Local APIs |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on duendesoftware/products: 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.