Read 2026-10-23
invoiceplane/invoiceplane: technical due diligence, read from its repository
What Borehole read in invoiceplane/invoiceplane's code and history at ef00e30: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
adequateassets/core/js/jquery-ui.js is 6,749 lines, 81× this codebase's median file
adequateThe median source file here is 83 lines. 1 file exceed 1,000 lines, the largest being 6,749. 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.
assets/core/js/jquery-ui.js:1 — 6,749 lines (81× median) |
1 base image floats: no version, or `latest`
adequate1 of 4 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
resources/docker/phpmyadmin/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
adequateTests are absent or token
adequate0 test files against 434 source files (0.0%). 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.
| 0 test files / 434 source files |
Product & Engineering Maturity
strongNode.js 18 is past end of life
adequateThe code is pinned to Node.js 18 (end of life 2025-04-30). None of these receives security fixes any more; the first stopped on 2025-04-30. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
.node-version — Node.js 18, end of life 2025-04-30 |
Releases are cut from another branch than the one surveyed
adequateThe newest pre-release, v2.0.0-alpha.1, is not on the branch this survey read; the newest release on it is v1.7.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.0.0-alpha.1 |
Security & Reliability Posture
adequate4 Dockerfiles run 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.
resources/docker/mariadb/Dockerfile — runs as root |
resources/docker/nginx/Dockerfile — runs as root |
resources/docker/php-fpm/Dockerfile — runs as root |
resources/docker/phpmyadmin/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate6 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/composer-update.yml:100 — action pinned by tag |
.github/workflows/crowdin-sync.yml:46 — action pinned by tag |
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (PHP `unserialize`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
application/modules/sessions/models/Mdl_sessions.php:172 — code-executing deserialiser |
7 locked dependencies have published vulnerabilities, 11 high or critical
adequate7 of 267 locked dependencies match 21 published advisories in OSV, 11 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
1 vendored component 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.
application/third_party/index.html — 1 tracked files, no licence file |
61 advisories against this project in the last 24 months, 27 high or critical
adequateThe newest was published on 2026-10-15. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. GHSA-vm87-2qmm-rhg8 (moderate), GHSA-346c-gqqq-mrm2 (moderate), GHSA-g53q-v2pv-xr83 (moderate) and 3 more affect 1.7.2, the newest release, and not the surveyed commit: their fixes are in the surveyed commit, and whether a release cut elsewhere carries them could not be told. Answer lives in: the version you run. The record is incomplete: NVD: 2 records name InvoicePlane with nothing tying them to this repository (CVE-2019-7223, CVE-2023-23011).
| 2026-10-15: GHSA-hg6g-m4fp-7cj3 (high), fixed in 1.7.3: Password changes do not revoke existing sessions |
| 2026-10-15: GHSA-r59m-wgg6-h4pv (moderate): Unauthenticated Rate-Limiter Namespace Collision via Login Form |
| 2026-09-28: GHSA-4fxw-x7wr-x6qc (high): Primary Administrator Privilege Downgrade via `Users::form()` (Missing Object-Level Authorization) |
| 2026-09-28: GHSA-77hm-22wp-96wp (high): Incomplete Authorization Remediation in Users::form() Enables Primary Administrator Account Takeover via Email Reassignment and Password Recovery in 1.7.2 versi |
| 2026-09-28: GHSA-j89p-m59x-86r9 (high): Arbitrary local file read via mPDF file:// in the Sales-by-Year report (unescaped client VAT-ID) |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 524 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 524 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 524 files for 10 structured logging libraries; 0 matched |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on invoiceplane/invoiceplane: 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.