Read 2026-10-23
juicedata/juicefs: technical due diligence, read from its repository
What Borehole read in juicedata/juicefs's code and history at b2a3be7: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: AGPL-3.0 → Apache-2.0 (2022-01-11)
Architecture & Codebase — including AI provenance
adequatepkg/meta/sql.go is 6,378 lines, 47× this codebase's median file
adequateThe median source file here is 134 lines. 11 files exceed 1,340 lines, the largest being 6,378. 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.
pkg/meta/sql.go:1 — 6,378 lines (47× median) |
pkg/meta/redis.go:1 — 6,371 lines (47× median) |
pkg/meta/tkv.go:1 — 5,207 lines (38× median) |
pkg/meta/base.go:1 — 4,211 lines (31× median) |
pkg/sync/sync.go:1 — 2,560 lines (19× median) |
1 base image floats: no version, or `latest`
adequate1 of 1 `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.
sdk/python/Dockerfile.builder:1 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate104 direct dependencies in a single manifest
adequatego.mod declares 104 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 104 declared |
package.json — 6 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.4.2, is not on the branch this survey read; the newest release on it is v0.13.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.4.2 |
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. 2 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 2 cited: JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate17 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; 6 steps pipe a download straight into a shell. 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/cache.yml:84 — action pinned by tag |
.github/workflows/cache.yml:94 — action pinned by tag |
.github/scripts/start_meta_engine.sh:103 — download piped into a shell |
15 locked dependencies have published vulnerabilities, 24 high or critical in what ships
adequate15 of 414 locked dependencies match 72 published advisories in OSV, 42 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.
go.mod — github.com/minio/minio v0.0.0-20210206053228-97fe57bba92c: GHSA-5cx5-wh4m-82fh (critical); pinned to a commit or a branch, so whether it has the fix needs the dependency's own source |
go.mod — github.com/prometheus/prometheus v0.54.1: GHSA-8rm2-7qqf-34qm (high), fixed in 0.311.3 |
go.mod — go.etcd.io/etcd v3.3.27+incompatible: GHSA-q8m4-xhhv-38mg (high) |
Relicensed: AGPL-3.0 → Apache-2.0 (2022-01-11)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
2 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-08-21. 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 commit. CVE-2026-59092 (high) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.
| 2026-08-21: CVE-2026-77763 (high): The filestore backend in pkg/object/file.go, used for file:// stores and as a common juicefs sync destination, derived every operation's target from path(key), |
| 2026-07-02: CVE-2026-59092 (high): JuiceFS through 1.3.1, fixed in commit a46979c, contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access sensitive |
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 |
1 of 1 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/juicefs-s3-gateway.yaml:39 — image without a version |
1 of 1 deployments run a single replica
adequate1 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
deploy/juicefs-s3-gateway.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on juicedata/juicefs: 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.