Read 2026-11-03
manyfold3d/manyfold: technical due diligence, read from its repository
What Borehole read in manyfold3d/manyfold's code and history at b7e33df: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE.md: Relicensed: MIT → AGPL-3.0 (2026-03-16).github/CONTRIBUTING.md:30: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
adequateapp/frontend/javascript/src/orbit_controls.js is 1,251 lines, 54× this codebase's median file
adequateThe median source file here is 23 lines. 1 file exceed 1,000 lines, the largest being 1,251. 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.
app/frontend/javascript/src/orbit_controls.js:1 — 1,251 lines (54× median) |
4 base images float: no version, or `latest`
adequate4 of 5 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
docker/build.dockerfile:3 — base image without a version |
docker/manyfold-solo.dockerfile:9 — base image without a version |
docker/manyfold.dockerfile:9 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate20% of bug fixes add or change a test
adequateOf 402 fixes in the last 24 months, 80 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 80 of 402 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate6 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/auto_merge.yml:17 — action pinned by tag |
.github/workflows/docker.yml:41 — action pinned by tag |
8 locked dependencies have published vulnerabilities, 23 high or critical
adequate8 of 975 locked dependencies match 34 published advisories in OSV, 23 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.
yarn.lock — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
Gemfile.lock — rubyzip 2.4.1: GHSA-47m2-wp7j-p9vc (high), fixed in 3.4.0 |
yarn.lock — brace-expansion 2.0.1: GHSA-3jxr-9vmj-r5cp (high), fixed in 2.1.2 |
Relicensed: MIT → AGPL-3.0 (2026-03-16)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.md — MIT from 2021-02-09 |
LICENSE.md — AGPL-3.0 from 2026-03-16 |
15 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-09-23. 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.153.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-23: GHSA-fv36-676v-7q87 (high), fixed in >= 0.150.0: Moderator can mint OAuth tokens for an administrator-owned application and impersonate that administrator |
| 2026-09-23: GHSA-v5cc-4c8x-p9ch (moderate), fixed in >= 0.150.0: File conversion endpoint authorizes visibility instead of update access to the source model |
| 2026-09-23: GHSA-rr5p-5cjh-2hgr (moderate), fixed in >= 0.150.0: Anonymous group creation and user invitation occur before authorization |
| 2026-09-23: GHSA-wrp9-pgg3-7257 (moderate), fixed in >= 0.150.0: Unscoped creator assignment lets contributors publish and impersonate another user's private creator |
| 2026-09-23: GHSA-pc85-5v23-xxfg (high), fixed in >= 0.150.0: OAuth scope validation lets restricted tokens read private data and invoke destructive actions |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,183 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,183 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 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 3 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.
docker-compose.example.yml:6 — 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 manyfold3d/manyfold: 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.