Read 2026-11-03
sync-in/server: technical due diligence, read from its repository
What Borehole read in sync-in/server's code and history at a2d3db6: 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
LICENSE:1: The licence is AGPL-3.0 with additional termsAI_POLICY.md:1: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongbackend/src/applications/shares/services/shares-manager.service.ts is 1,264 lines, 28× this codebase's median file
adequateThe median source file here is 45 lines. 3 files exceed 1,000 lines, the largest being 1,264. 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/src/applications/shares/services/shares-manager.service.ts:1 — 1,264 lines (28× median) |
frontend/src/app/applications/spaces/components/spaces-browser.component.ts:1 — 1,186 lines (26× median) |
backend/src/applications/shares/services/shares-queries.service.ts:1 — 1,115 lines (24× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 99 of 1,119 commits (8.8%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 99 of 1,119 commits in the last 24 months carry review evidence; 8.8% across all 1,119 |
Product & Engineering Maturity
strongNo finding.
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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate3 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/release.yml:38 — action pinned by tag |
.github/workflows/release.yml:44 — action pinned by tag |
4 locked dependencies have published vulnerabilities
adequate4 of 551 locked dependencies match 4 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.
package-lock.json — esbuild 0.18.20: GHSA-67mh-4wv8-2f99 (moderate), fixed in 0.25.0 |
package-lock.json — glob 13.0.6: GHSA-3g3m-2fjr-6pw4 (moderate), fixed in 14.0.2 |
package-lock.json — minimatch 10.2.6: GHSA-g3hv-75wg-m249 (moderate), fixed in 11.0.1 |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
frontend/angular.json:74 — source maps in a production build |
The licence is AGPL-3.0 with additional terms
adequateLICENSE grants AGPL-3.0 with additional terms: open source; offering it over a network counts as distributing it, so a hosted product's changes must be published. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 660 lines, AGPL-3.0 AND LicenseRef-Terms-Additional |
18 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-10-25. 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. The record is incomplete: NVD: its keyword search for 'server' is too broad to read whole (42,497 records); NVD: 923 records name server with nothing tying them to this repository (CVE-1999-0070, CVE-1999-0079, CVE-1999-0103, …).
| 2026-10-25: GHSA-759w-893m-w4rp (moderate), fixed in 2.6.1: pathFilters ReDoS via safe-regex2 bypass (incomplete fix of GHSA-jx63-h26r-8cph) |
| 2026-09-14: GHSA-phhw-76pc-crgg (moderate), fixed in 2.5.1: Non-atomic access counter allows concurrent requests to exceed public-link limits |
| 2026-09-02: GHSA-4rg7-mqpm-cgf2 (moderate), fixed in 2.5.0: OnlyOffice callback filename/md5 parameters allow path traversal out of the temp directory |
| 2026-09-02: GHSA-g732-49pc-5rh3 (low), fixed in 2.5.0: Uploaded SVG thumbnails can render referenced files from the same directory |
| 2026-09-02: GHSA-fgr8-f8r9-qh38 (moderate), fixed in 2.5.0: Unbounded WebDAV PUT Without Content-Length Can Bypass Storage Quotas |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,107 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 1,107 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 |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 |
2 of 8 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/config/collabora/docker-compose.collabora.yaml:3 — image without a version |
docker/config/drawio/docker-compose.drawio.yaml:3 — 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 sync-in/server: 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.