Read 2026-11-03
tolgee/tolgee-platform: technical due diligence, read from its repository
What Borehole read in tolgee/tolgee-platform's code and history at e953d93: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
ee/LICENSE: Part of the code is under a separate licence: ee/, webapp/src/ee/
Architecture & Codebase — including AI provenance
strongbackend/data/src/main/kotlin/io/tolgee/formats/pluralData/PluralData.kt is 2,823 lines, 62× this codebase's median file
adequateThe median source file here is 45 lines. 1 file exceed 1,000 lines, the largest being 2,823. 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.
backend/data/src/main/kotlin/io/tolgee/formats/pluralData/PluralData.kt:1 — 2,823 lines (62× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/cypress/e2e/languages/aiCustomization.cy.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
e2e/cypress/e2e/languages/aiCustomization.cy.ts:24 — test retry |
5% of recent commits change more than 2,000 lines
adequate37 of 724 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.
| 37 commits over 2,000 lines |
Product & Engineering Maturity
strong7 files still carry code deprecated more than two years ago
adequate7 files were marked deprecated over two years ago and still are, the oldest since Jun 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
backend/data/src/main/kotlin/io/tolgee/model/MtCreditBucket.kt — deprecated since Jun 2022 |
backend/data/src/main/kotlin/io/tolgee/model/Project.kt — deprecated since Jun 2022 |
backend/data/src/main/kotlin/io/tolgee/dtos/request/key/ComplexEditKeyDto.kt — deprecated since Feb 2023 |
backend/data/src/main/kotlin/io/tolgee/dtos/request/key/CreateKeyDto.kt — deprecated since Feb 2023 |
backend/data/src/main/kotlin/io/tolgee/development/DbPopulatorReal.kt — deprecated since May 2023 |
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
docker/app/Dockerfile — runs as root |
3 environment files are committed
adequatedocker/.env, library/.env, webapp/.env.production are tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
docker/.env — committed environment file |
library/.env — committed environment file |
webapp/.env.production — committed environment file |
The 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/preview.yml:58 — action pinned by tag |
.github/workflows/reportIntermittentTests.yml:81 — action pinned by tag |
9 locked dependencies have published vulnerabilities, 6 high or critical in what ships
adequate9 of 686 locked dependencies match 21 published advisories in OSV, 10 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.
webapp/package-lock.json — brace-expansion 1.1.13: GHSA-3jxr-9vmj-r5cp (high), fixed in 1.1.16 |
webapp/package-lock.json — minimatch 3.1.3: GHSA-23c5-xmqv-rm74 (high), fixed in 3.1.4 |
webapp/package-lock.json — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10; reached only by the build |
Part of the code is under a separate licence: ee/, webapp/src/ee/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
ee/LICENSE — licence: unrecognised |
webapp/src/ee/LICENSE — licence: unrecognised |
4 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-06-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. None of them affects the surveyed version.
| 2026-06-02: GHSA-535f-x3hw-p4p8 (high), fixed in > 3.194.0: Broken object-level authorization across EE/project resources (BOLA) |
| 2026-06-02: GHSA-4mw7-vff5-96jj (high), fixed in > 3.194.0: Unauthenticated Slack bot-event signature bypass allows deleting a workspace integration |
| 2026-03-11: GHSA-rcvv-64pq-vxfx (critical): XXE Injection in Translation Import |
| 2024-11-12: GHSA-3wr3-889v-pgcj (critical), fixed in v3.81.2: Configuration all configuration properties leaked in public configuration DTO |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 5,273 files for 10 structured logging libraries; 0 matched |
2 of 3 deployed images carry no version, or `latest`
adequate2 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker/docker-compose.yml:9 — image without a version |
docker/docker-compose.yml:17 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on tolgee/tolgee-platform: 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.