Borehole · Project · free tier
teslamate-org/teslamate
Free reading: not for reliance
1ddb3e4 · 3,272 commits · 922 files
Read 2026-10-04

teslamate-org/teslamate: technical due diligence, read from its repository

What Borehole read in teslamate-org/teslamate's code and history at 1ddb3e4: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsadequate
Fit with the Acquirernot assessable

What the repository says

  • LICENSE: Relicensed: MIT → AGPL-3.0 (2026-02-13)
  • README.md:4: names OpenSSF

Architecture & Codebase — including AI provenance

strong
01.6

elixir/lib/teslamate/vehicles/vehicle.ex is 2,251 lines, 50× this codebase's median file

adequate

The median source file here is 45 lines. 2 files exceed 1,000 lines, the largest being 2,251. 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.

Evidence
elixir/lib/teslamate/vehicles/vehicle.ex:1 — 2,251 lines (50× median)
elixir/lib/teslamate/mqtt/pubsub/home_assistant.ex:1 — 1,111 lines (24× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.17

Node.js 20 is past end of life

adequate

The code is pinned to Node.js 20 (end of life 2026-04-30). None of these receives security fixes any more; the first stopped on 2026-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.

Evidence
.node-version — Node.js 20, end of life 2026-04-30

Security & Reliability Posture

adequate
05.26

9 locked dependencies have published vulnerabilities, 1 high or critical in what ships

adequate

9 of 1,345 locked dependencies match 15 published advisories in OSV, 5 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.

Evidence
website/package-lock.json — braces 3.0.3: GHSA-vfj7-8cjw-p6xm (high)
website/package-lock.json — brace-expansion 1.1.18: GHSA-6j4f-fj2g-mc7p (high), fixed in 1.1.19; reached only by the build
website/package-lock.json — http-cache-semantics 4.2.0: GHSA-ch52-4w7c-c8xp (high); reached only by the build
05.60

Relicensed: MIT → AGPL-3.0 (2026-02-13)

adequate

The root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.

Evidence
LICENSE — MIT from 2019-07-24
LICENSE — AGPL-3.0 from 2026-02-13

Observability & Operations

adequate
06.1

No telemetry or error reporting is wired in anywhere

adequate

None of 787 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.

Evidence
searched 787 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
06.8

One request cannot be followed through the logs

adequate

Nothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.

Evidence
no request id, correlation id or tracing found
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on teslamate-org/teslamate: 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.