Read 2026-11-03
evcc-io/evcc: technical due diligence, read from its repository
What Borehole read in evcc-io/evcc's code and history at 12ce81c: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:14: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongcore/loadpoint.go is 2,787 lines, 32× this codebase's median file
adequateThe median source file here is 87 lines. 11 files exceed 1,000 lines, the largest being 2,787. 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.
core/loadpoint.go:1 — 2,787 lines (32× median) |
assets/js/views/Config.vue:1 — 1,891 lines (21× median) |
core/site_optimizer.go:1 — 1,806 lines (20× median) |
assets/js/types/evcc.ts:1 — 1,659 lines (19× median) |
core/site.go:1 — 1,650 lines (18× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
playwright.config.ts:10 — test retry |
Product & Engineering Maturity
adequate112 direct dependencies in a single manifest
adequatego.mod declares 112 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 112 declared |
package.json — 22 declared |
17% of bug fixes add or change a test
adequateOf 878 fixes in the last 24 months, 151 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.
| 151 of 878 |
12 files still carry code deprecated more than two years ago
adequate12 files were marked deprecated over two years ago and still are, the oldest since Feb 2024. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
vehicle/mercedes/pb/acp.pb.go — deprecated since Feb 2024 |
vehicle/mercedes/pb/client.pb.go — deprecated since Feb 2024 |
vehicle/mercedes/pb/cluster.pb.go — deprecated since Feb 2024 |
vehicle/mercedes/pb/eventpush.pb.go — deprecated since Feb 2024 |
vehicle/mercedes/pb/protos/protos.pb.go — deprecated since Feb 2024 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 0.318.2, is not on the branch this survey read; the newest release on it is 0.318.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 0.318.2 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key. 5 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| private key block, where fakes are usual |
1 Dockerfile runs 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.
Dockerfile — runs as root |
1 SQL statement built from strings
adequate1 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
server/http_site_handler.go:648 — SQL built from a string |
1 locked dependency has published vulnerabilities, 4 high or critical
adequate1 of 519 locked dependencies match 21 published advisories in OSV, 4 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. None of the high or critical ones is in what the product ships: only the build reaches them: a bundler, a code generator, a build plugin, or a lockfile in a tooling directory.
package-lock.json — vite 1.3.0: GHSA-353f-5xf4-qw67 (high), fixed in 2.9.16; reached only by the build |
Observability & Operations
strongNo 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 evcc-io/evcc: 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.