Read 2026-10-23
cachethq/cachet: technical due diligence, read from its repository
What Borehole read in cachethq/cachet's code and history at 40bd081: 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
- No release for 36 months while development continues
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate44% of commit subjects are exact repeats of another subject, and subject length varies by only 14.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.
| 118× 'Apply fixes from StyleCI' |
| 101× 'Updated dependencies' |
| 60× 'Update deps' |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate3 test files against 38 source files (7.9%). 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.
| 3 test files / 38 source files |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.52 to 1.01 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.52, second half 1.01 (split 2020-10-26) |
No release for 36 months while development continues
adequateThe last tag, v2.4.1, was cut 1080 days before the survey; the typical gap between releases was 48 days, and 29 commits landed in the last 90 days. Users run the last release, not this code.
| last tag v2.4.1 |
Security & Reliability Posture
adequateLicence text does not match a standard licence
adequateLICENSE.md 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.md:1 — 50 lines, unrecognised |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-27. 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 2 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.4.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names cachet with nothing tying it to this repository (CVE-2021-39165).
| 2026-08-27: GHSA-x397-5hrv-j9m9 (moderate): Stored XSS in Incident Component |
| 2026-08-10: CVE-2026-69118 (high): Cachet through 2.4.1 contains a server-side template injection vulnerability in incident template rendering that allows authenticated users to execute arbitrary |
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 cachethq/cachet: 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.