Read 2026-11-03
refly-ai/refly: technical due diligence, read from its repository
What Borehole read in refly-ai/refly's code and history at 80de1cb: 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
LICENSE:1: The licence is Apache-2.0 with terms on offering it as a service
Architecture & Codebase — including AI provenance
strongpackages/i18n/src/zh-Hans/ui.ts is 5,021 lines, 51× this codebase's median file
adequateThe median source file here is 97 lines. 36 files exceed 1,000 lines, the largest being 5,021. 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.
packages/i18n/src/zh-Hans/ui.ts:1 — 5,021 lines (51× median) |
packages/i18n/src/en-US/ui.ts:1 — 5,011 lines (51× median) |
packages/ai-workspace-common/src/queries/queries.ts:1 — 3,539 lines (36× median) |
packages/ai-workspace-common/src/modules/artifacts/code-runner/render/shadcn.ts:1 — 3,100 lines (31× median) |
apps/api/src/modules/drive/drive.service.ts:1 — 2,980 lines (30× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate92 test files against 1,456 source files (6.3%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 92 test files / 1,456 source files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (cypress.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
cypress.config.ts:9 — test retry |
Product & Engineering Maturity
adequate111 direct dependencies in a single manifest
adequatepackages/ai-workspace-common/package.json declares 111 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.
packages/ai-workspace-common/package.json — 111 declared |
apps/api/package.json — 105 declared |
packages/web-core/package.json — 27 declared |
packages/utils/package.json — 20 declared |
3% of bug fixes add or change a test
adequateOf 1411 fixes in the last 24 months, 40 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.
| 40 of 1411 |
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 1,993 tracked files; 0 present |
4 Dockerfiles run 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.
apps/api/Dockerfile — runs as root |
apps/web/Dockerfile — runs as root |
deploy/docker/elasticsearch/Dockerfile — runs as root |
deploy/docker/qdrant/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate9 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/build-image-release.yml:69 — action pinned by tag |
.github/workflows/build-image-release.yml:72 — action pinned by tag |
4 shell commands built from strings
adequate4 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
apps/api/src/utils/prisma.ts:51 — command run through a shell |
apps/api/src/utils/prisma.ts:71 — command run through a shell |
packages/cli/src/commands/upgrade.ts:70 — command run through a shell |
97 locked dependencies have published vulnerabilities, 54 high or critical in what ships
adequate97 of 3,821 locked dependencies match 172 published advisories in OSV, 87 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.
pnpm-lock.yaml — basic-ftp 5.1.0: GHSA-5rq4-664w-9x2c (critical), fixed in 5.2.0 |
pnpm-lock.yaml — handlebars 4.7.8: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9 |
pnpm-lock.yaml — happy-dom 15.11.7: GHSA-37j7-fg3j-429f (critical), fixed in 20.0.0; a development dependency |
7 places insert HTML from a variable without sanitising it
adequate7 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
packages/ai-workspace-common/src/components/editor/components/extensions.ts:69 — HTML from a variable |
packages/ai-workspace-common/src/components/editor/components/extensions.ts:85 — HTML from a variable |
packages/ai-workspace-common/src/components/editor/components/extensions.ts:92 — HTML from a variable |
The licence is Apache-2.0 with terms on offering it as a service
adequateLICENSE grants Apache-2.0 with terms on offering it as a service: 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 — 49 lines, Apache-2.0 AND LicenseRef-Terms-Service |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-09-14. 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 1.1.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names refly with nothing tying it to this repository (CVE-2026-101052).
| 2026-09-14: CVE-2026-91199 (moderate): Refly through 1.1.0 contains a server-side request forgery vulnerability in the POST /v1/misc/scrape endpoint that fetches caller-supplied URLs without validati |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 1,806 files for 10 structured logging libraries; 0 matched |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on refly-ai/refly: 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.