Read 2026-10-23
semantica-agi/semantica: technical due diligence, read from its repository
What Borehole read in semantica-agi/semantica's code and history at 22109ee: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
README.md:29: names OpenSSF
Architecture & Codebase — including AI provenance
strongsemantica/cli.py is 6,358 lines, 22× this codebase's median file
adequateThe median source file here is 278 lines. 6 files exceed 2,780 lines, the largest being 6,358. 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.
semantica/cli.py:1 — 6,358 lines (22× median) |
semantica/context/context_graph.py:1 — 5,928 lines (21× median) |
semantica/explorer/routes/ontology.py:1 — 3,793 lines (13× median) |
explorer/src/workspaces/GraphWorkspace/GraphWorkspace.tsx:1 — 3,585 lines (12× median) |
semantica/context/context_retriever.py:1 — 3,343 lines (12× median) |
Engineering Process & SDLC Maturity
adequate9% of recent commits change more than 2,000 lines
adequate184 of 2126 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.
| 184 commits over 2,000 lines |
Product & Engineering Maturity
adequateFixes are 54% of recent work, up from 18%
adequateIn the last two quarters 54% of commits were fixes, against 18% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 64%, 43%, 46%, 27%, 0%, 0% |
Security & Reliability Posture
adequate6 SQL statements built from strings
adequate6 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
semantica/provenance/storage.py:950 — SQL built from a string |
semantica/vector_store/sqlite_vec_store.py:311 — SQL built from a string |
semantica/vector_store/sqlite_vec_store.py:327 — SQL built from a string |
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
semantica/context/context_graph.py:2135 — code-executing deserialiser |
4 locked dependencies have published vulnerabilities, 27 high or critical in what ships
adequate4 of 671 locked dependencies match 44 published advisories in OSV, 30 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.
uv.lock — pillow 12.3.0: GHSA-332p-7hrc-92wf (critical), fixed in 13.0.0 |
explorer/package-lock.json — dompurify 3.4.16: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17; reached only by the build |
uv.lock — nbconvert 7.17.1: GHSA-pjvx-prjx-h659 (high), fixed in 7.17.2; a development dependency |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-11. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| 2026-08-11: GHSA-8c7v-62gr-hj6g (high): semantica: unvalidated redirect targets in ontology URL fetching allow remote attackers to read internal network resources |
Observability & Operations
adequateNo 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 |
1 of 2 deployed images carry no version, or `latest`
adequate1 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.
deploy/gcp/cloudrun-service.yaml:25 — image without a version |
Readiness and liveness probes are identical in 3 of 3 workloads
adequateBoth probes call the same endpoint. When a dependency slows down, the liveness probe fails with the readiness probe, so the platform restarts pods that only needed taking out of rotation, and a partial outage becomes a full one. Liveness should ask whether the process is alive; readiness whether it can serve.
deploy/helm/knowledge-explorer/templates/deployment.yaml — same probe endpoint twice |
deploy/helm/knowledge-explorer/values.yaml — same probe endpoint twice |
deploy/kubernetes/deployment.yaml — same probe endpoint twice |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on semantica-agi/semantica: 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.