Read 2026-10-23
faveosuite/faveo-helpdesk: technical due diligence, read from its repository
What Borehole read in faveosuite/faveo-helpdesk's code and history at 408076c: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate52% of commit subjects are exact repeats of another subject, and subject length varies by only 9.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.
| 117× 'Apply fixes from StyleCI' |
| 59× 'Update README.md' |
| 39× 'Applied fixes from StyleCI' |
DB/demodatabase.sql is 3,426 lines, 69× this codebase's median file
adequateThe median source file here is 49 lines. 24 files exceed 1,000 lines, the largest being 3,426. 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.
DB/demodatabase.sql:1 — 3,426 lines (69× median) |
DB/dummy-data.sql:1 — 3,426 lines (69× median) |
app/Http/Controllers/Agent/helpdesk/TicketController.php:1 — 3,242 lines (66× median) |
resources/views/themes/default1/agent/helpdesk/ticket/timeline.blade.php:1 — 2,303 lines (47× median) |
database/seeders/v_2_0_0/DatabaseSeeder.php:1 — 2,054 lines (41× median) |
380 errors caught and discarded in product code
adequate380 places catch an error and do nothing with it, across 73 files (0.9 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
app/Api/v1/ApiController.php:86 — error caught and discarded |
app/Api/v1/ApiController.php:87 — error caught and discarded |
app/Api/v1/TicketController.php:374 — error caught and discarded |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate143 test files against 1,937 source files (7.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.
| 143 test files / 1,937 source files |
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.31 to 0.83 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.31, second half 0.83 (split 2019-08-24) |
Security & Reliability Posture
adequate2 credential-shaped strings committed to the tree
adequateMatches for Google API key appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. Only Google API keys matched. Those are often public by design, in a browser app's Firebase or Maps configuration; the question is whether each is restricted to the app's domains and APIs.
| 2 cited: Google API key pattern matched |
4 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
public/vendor/datatables — 1 tracked files, no licence file |
vendor/autoload.php — 1 tracked files, no licence file |
vendor/bin — 12 tracked files, no licence file |
vendor/neitanod — 4 tracked files, no licence file |
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 47 lines, unrecognised |
3 advisories against this project in the last 24 months
adequateThe newest was published on 2026-10-16. 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 2.0.3. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 4 records name faveo-helpdesk with nothing tying them to this repository (CVE-2023-1724, CVE-2023-25350, CVE-2024-51377, …).
| 2026-10-16: CVE-2026-111676 (moderate): Faveo Helpdesk through 2.0.3 contains a broken access control vulnerability that allows authenticated agents to read tickets in other departments via the getToo |
| 2026-08-24: CVE-2026-78434 (moderate): A flaw has been found in Faveo Helpdesk up to 2.0.3. This impacts the function FormController::post_ticket_reply of the file app/Http/Controllers/Client/helpdes |
| 2026-08-24: CVE-2026-78435 (low): A vulnerability has been found in Faveo Helpdesk up to 2.0.3. Affected is the function unlink of the file app/Http/Controllers/Admin/helpdesk/SettingsController |
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 faveosuite/faveo-helpdesk: 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.