Read 2026-10-23
gethomepage/homepage: technical due diligence, read from its repository
What Borehole read in gethomepage/homepage's code and history at ba1db58: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:53: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate65% of commit subjects are exact repeats of another subject, and subject length varies by only 13.9 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.
| 243× 'Translated using Weblate (Spanish)' |
| 236× 'Translated using Weblate (French)' |
| 157× 'Translated using Weblate (Chinese (Simplified))' |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
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 |
6 locked dependencies have published vulnerabilities, 5 high or critical
adequate6 of 808 locked dependencies match 9 published advisories in OSV, 5 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. None of the high or critical ones is in what the product ships: they are development dependencies.
pnpm-lock.yaml — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10; a development dependency |
pnpm-lock.yaml — js-yaml 4.3.1: GHSA-2883-xcg3-v3hh (high), fixed in 4.3.2; a development dependency |
pnpm-lock.yaml — nanoid 3.3.17: GHSA-2v37-7h3g-55p8 (high), fixed in 3.3.18; a development dependency |
4 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-10-17. 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 version. The record is incomplete: NVD: 98 records name homepage with nothing tying them to this repository (CVE-2002-1427, CVE-2006-1023, CVE-2006-1774, …).
| 2026-10-17: GHSA-qxcr-4rv3-v23r (high), fixed in 2.6.0: Authentication gate bypass via Next.js on-demand revalidation header |
| 2026-09-02: GHSA-669x-4pg4-w24r (moderate), fixed in 2.2.0: Homepage service proxy allows client-controlled methods and bodies to configured widget endpoints |
| 2026-04-01: GHSA-rg3r-jprv-xq38 (moderate), fixed in 1.12.3: Path Traversal and Endpoint Bypass in Glances Widget Handler |
| 2025-08-13: GHSA-c4qv-fm8g-wm67 (moderate), fixed in v1.4.5: Arbitrary Path Existence Disclosure in Resources Endpoint |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on gethomepage/homepage: 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.