Read 2026-11-03
hulaspark/hula: technical due diligence, read from its repository
What Borehole read in hulaspark/hula's code and history at 1ba8de8: 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 | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongsrc/plugins/robot/views/Chat.vue is 3,479 lines, 28× this codebase's median file
adequateThe median source file here is 120 lines. 9 files exceed 1,200 lines, the largest being 3,479. 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.
src/plugins/robot/views/Chat.vue:1 — 3,479 lines (28× median) |
src/components/common/Screenshot.vue:1 — 1,665 lines (13× median) |
src/stores/chat.ts:1 — 1,463 lines (12× median) |
src/hooks/useMsgInput.ts:1 — 1,374 lines (11× median) |
src/hooks/useChatMain.ts:1 — 1,359 lines (11× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate5 test files against 473 source files (1.1%). 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 / 473 source files |
Product & Engineering Maturity
adequate1% of bug fixes add or change a test
adequateOf 446 fixes in the last 24 months, 4 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.
| 4 of 446 |
Security & Reliability Posture
strong1 environment file is committed
adequate.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
.env — committed environment file |
The build runs third-party code it does not pin
adequate5 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/debug-build.yml:45 — action pinned by tag |
.github/workflows/debug-build.yml:72 — action pinned by tag |
5 places insert HTML from a variable without sanitising it
adequate5 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.
public/icon.js:1 — HTML from a variable |
src/components/rightBox/chatBox/Bot.vue:85 — HTML from a variable |
src/components/rightBox/renderMessage/special/RecallMessage.vue:11 — HTML from a variable |
3 advisories against this project in the last 24 months
adequateThe newest was published on 2026-10-30. 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 3 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 3.0.9. Answer lives in: the release you run, set against each fixed version.
| 2026-10-30: CVE-2026-119650 (moderate): HuLa-Server through 3.0.7 contains an insecure direct object reference vulnerability in PrivacyController that allows authenticated users to access other users' |
| 2026-10-30: CVE-2026-119651 (moderate): HuLa-Server through 3.0.7 contains an insecure direct object reference vulnerability in FeedController.delFeed that allows authenticated users to delete other u |
| 2026-10-30: CVE-2026-119652 (moderate): HuLa-Server through 3.0.7 contains an insecure direct object reference vulnerability in FriendController.friendList that allows authenticated users to view othe |
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 hulaspark/hula: 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.