Read 2026-11-03
lynpoint/cyberverse: technical due diligence, read from its repository
What Borehole read in lynpoint/cyberverse's code and history at f624742: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongserver/internal/orchestrator/orchestrator.go is 5,075 lines, 38× this codebase's median file
adequateThe median source file here is 131 lines. 10 files exceed 1,310 lines, the largest being 5,075. 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.
server/internal/orchestrator/orchestrator.go:1 — 5,075 lines (38× median) |
frontend/src/pages/OfflineVideoPage.vue:1 — 2,204 lines (16× median) |
frontend/src/pages/CharacterEditPage.vue:1 — 1,938 lines (14× median) |
frontend/src/pages/SessionPage.vue:1 — 1,825 lines (13× median) |
models/SoulX-LiveAct/lightx2v/models/video_encoders/hf/wan/vae.py:1 — 1,631 lines (12× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 16 of 209 commits (7.7%) 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.
| 16 of 209 commits in the last 24 months carry review evidence; 7.7% across all 209 |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — none are present. 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.
| 0 of 5 markers present across 533 tracked files |
9% of recent commits change more than 2,000 lines
adequate17 of 189 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.
| 17 commits over 2,000 lines |
Product & Engineering Maturity
not assessableNot rated: only 9 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
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 533 tracked files; 0 present |
1 environment file is committed
adequatefrontend/.env.production is 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.
frontend/.env.production — committed environment file |
2 deserialisers that can run code
adequate2 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
models/MuseTalk/app.py:260 — code-executing deserialiser |
models/MuseTalk/musetalk/loss/vgg_face.py:31 — code-executing deserialiser |
32 locked dependencies have published vulnerabilities, 12 high or critical in what ships
adequate32 of 527 locked dependencies match 124 published advisories in OSV, 64 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
server/go.mod — golang.org/x/crypto v0.48.0: GHSA-5cgq-3rg8-m6cv (critical), fixed in 0.52.0 |
uv.lock — anyio 4.14.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2; an optional extra |
uv.lock — brotli 1.2.0: GHSA-9v8h-qqgm-4m35 (critical), fixed in 1.2.1; an optional extra |
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 lynpoint/cyberverse: 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.