Read 2026-11-03
genspark-ai/genoffice: technical due diligence, read from its repository
What Borehole read in genspark-ai/genoffice's code and history at e1f50e9: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:9: This repository is a mirror; development happens elsewhereee/LICENSE: Part of the code is under a separate licence: ee/
Architecture & Codebase — including AI provenance
strongapps/shell/src/renderer/src/strings.ts is 11,954 lines, 88× this codebase's median file
adequateThe median source file here is 135 lines. 93 files exceed 1,350 lines, the largest being 11,954. 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.
apps/shell/src/renderer/src/strings.ts:1 — 11,954 lines (88× median) |
apps/pdf/src/renderer/App.tsx:1 — 11,888 lines (88× median) |
apps/pdf/src/renderer/i18n/strings.ts:1 — 10,233 lines (75× median) |
packages/docx-engine/src/parse.ts:1 — 9,172 lines (67× median) |
apps/sheets/src/renderer/univer-sync.ts:1 — 8,269 lines (61× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (e2e/docs-spell-suggestions.spec.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/docs-spell-suggestions.spec.ts:64 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| AWS access key, where fakes are usual |
| GitHub token, where fakes are usual |
2 credential-shaped strings added in the history sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| AWS access key, where fakes are usual |
| GitHub token, where fakes are usual |
2 locked dependencies have published vulnerabilities
adequate2 of 647 locked dependencies match 3 published advisories in OSV. 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
apps/sheets/native/xlsx-engine/Cargo.lock — calamine 0.37.0: RUSTSEC-2026-0436 (unrated), fixed in 0.38.0 |
apps/sheets/native/xlsx-engine/Cargo.lock — quick-xml 0.38.4: RUSTSEC-2026-0194 (unrated), fixed in 0.41.0 |
9 places insert HTML from a variable without sanitising it
adequate9 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
apps/html/src/renderer/preview/inspector.js:520 — HTML from a variable |
apps/markdown/src/renderer/editor/CodeBlockView.tsx:186 — HTML from a variable |
apps/markdown/src/renderer/editor/blockDragHandle.ts:56 — HTML from a variable |
Part of the code is under a separate licence: 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 |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-10-10. 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 1 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.12.600. Answer lives in: the release you run, set against each fixed version.
| 2026-10-10: CVE-2026-108582 (moderate): GenOffice through 0.11.505 contains an incorrect permissions vulnerability in its HTTP MCP server file store that allows local unprivileged users to read upload |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 5,668 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 5,668 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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,668 files for 10 structured logging libraries; 0 matched |
No 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 genspark-ai/genoffice: 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.