Read 2026-10-04
hiddify/hiddify-app: technical due diligence, read from its repository
What Borehole read in hiddify/hiddify-app's code and history at 276a7ef: 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 | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE.md:1: The licence is GPL-3.0 with a non-commercial condition and an attribution term: source available, not open sourceLICENSE.md: Relicensed: CC-BY-NC-SA-4.0 → GPL-3.0 with a non-commercial condition and an attribution term (2024-10-29).gitmodules:1: 1 submodule(s) this survey does not read: hiddify-core
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate35% of commit subjects are exact repeats of another subject, and subject length varies by only 41.5 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 158× 'inlang: update translations' |
| 108× 'Update README.md' |
| 69× 'Update README_fa.md' |
web/drift_worker.js is 13,320 lines, 261× this codebase's median file
adequateThe median source file here is 51 lines. 2 files exceed 1,000 lines, the largest being 13,320. 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.
web/drift_worker.js:1 — 13,320 lines (261× median) |
lib/features/profile/details/json_editor.dart:1 — 1,689 lines (33× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate5 test files against 367 source files (1.4%). 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.
| 5 test files / 367 source files |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.46 to 0.87 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.46, second half 0.87 (split 2024-12-03) |
2% of bug fixes add or change a test
adequateOf 243 fixes in the last 24 months, 5 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.
| 5 of 243 |
Security & Reliability Posture
adequate1 Dockerfile runs 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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate14 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/add_signed_microsft.yml:21 — action pinned by tag |
.github/workflows/build.yml:43 — action pinned by tag |
The licence is GPL-3.0 with a non-commercial condition and an attribution term: source available, not open source
adequateLICENSE.md grants GPL-3.0 with a non-commercial condition and an attribution term: source available, not open source; commercial use needs the licensor's consent. 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.md:1 — 609 lines, GPL-3.0 AND LicenseRef-Terms-NonCommercial AND LicenseRef-Terms-Attribution |
Relicensed: CC-BY-NC-SA-4.0 → GPL-3.0 with a non-commercial condition and an attribution term (2024-10-29)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
LICENSE.md — CC-BY-NC-SA-4.0 from 2023-07-21 |
LICENSE.md — GPL-3.0 with a non-commercial condition and an attribution term from 2024-10-29 |
Observability & Operations
not assessableNot rated: only 4 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on hiddify/hiddify-app: 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.