Read 2026-11-03
hugoblox/kit: technical due diligence, read from its repository
What Borehole read in hugoblox/kit's code and history at 68cbf33: 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 |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 46 source files (2.2%). 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.
| 1 test files / 46 source files |
5% of recent commits change more than 2,000 lines
adequate17 of 329 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 17 commits over 2,000 lines |
Product & Engineering Maturity
adequate2% of bug fixes add or change a test
adequateOf 116 fixes in the last 24 months, 2 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.
| 2 of 116 |
Security & Reliability Posture
adequateThe 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/ci-build-starters-matrix.yml:140 — action pinned by tag |
.github/workflows/devcontainer-image.yml:58 — action pinned by tag |
32 locked dependencies have published vulnerabilities, 24 high or critical in what ships
adequate32 of 718 locked dependencies match 124 published advisories in OSV, 43 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.
poetry.lock — certifi 2024.2.2: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
pnpm-lock.yaml — maplibre-gl 4.7.1: GHSA-jrc7-96c5-q579 (critical), fixed in 6.4.1; reached only by the build |
poetry.lock — urllib3 2.2.1: GHSA-2xpw-w6gg-jr37 (high), fixed in 2.6.0 |
94 places insert HTML from a variable without sanitising it
adequate94 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.
modules/blox/assets/js/hb-code-copy.js:64 — HTML from a variable |
modules/blox/assets/js/hb-code-copy.js:66 — HTML from a variable |
modules/blox/assets/js/hb-code-copy.js:77 — HTML from a variable |
Observability & Operations
not assessableNot rated: only 5 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 hugoblox/kit: 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.