Borehole · Project · free tier
encoredev/encore
Free reading: not for reliance
bd202f8 · 2,274 commits · 1,910 files
Read 2026-10-23

encoredev/encore: technical due diligence, read from its repository

What Borehole read in encoredev/encore's code and history at bd202f8: 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 Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsstrong
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

tsparser/src/parser/types/type_resolve.rs is 2,720 lines, 23× this codebase's median file

adequate

The median source file here is 117 lines. 17 files exceed 1,170 lines, the largest being 2,720. 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
tsparser/src/parser/types/type_resolve.rs:1 — 2,720 lines (23× median)
pkg/clientgen/typescript.go:1 — 2,392 lines (20× median)
runtimes/core/src/cache/client_tests.rs:1 — 2,190 lines (18× median)
miniredis/src/cmd/sorted_set.rs:1 — 1,687 lines (14× median)
miniredis/src/cmd/stream.rs:1 — 1,649 lines (14× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.3

81 direct dependencies in a single manifest

adequate

go.mod declares 81 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.

Evidence
go.mod — 81 declared
runtimes/go/go.mod — 44 declared
04.19

13% of bug fixes add or change a test

adequate

Of 143 fixes in the last 24 months, 19 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.

Evidence
19 of 143
04.38

11 files still carry code deprecated more than two years ago

adequate

11 files were marked deprecated over two years ago and still are, the oldest since Mar 2021. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

Evidence
proto/encore/daemon/daemon.pb.go — deprecated since Mar 2021
proto/encore/parser/schema/v1/schema.pb.go — deprecated since Mar 2021
proto/encore/parser/meta/v1/meta.pb.go — deprecated since Mar 2021
proto/encore/engine/trace/trace.pb.go — deprecated since Mar 2021
cli/internal/gosym/pclntab.go — deprecated since May 2021

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.

Evidence
checked 5 kinds of guard rail across 1,910 tracked files; 0 present
05.27

The build runs third-party code it does not pin

adequate

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

Evidence
.github/workflows/ci.yml:67 — action pinned by tag
.github/workflows/ci.yml:277 — action pinned by tag
05.13

14 outbound calls can wait forever

adequate

14 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

Evidence
cli/cmd/encore/bits/api.go:27 — outbound call without a timeout
cli/cmd/encore/bits/api.go:47 — outbound call without a timeout
cli/cmd/encore/llm_rules/tool.go:308 — outbound call without a timeout
05.20

2 SQL statements built from strings

adequate

2 places in product code build SQL by formatting or joining strings rather than passing parameters. 2 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.

Evidence
cli/daemon/engine/trace2/sqlite/write.go:145 — SQL built from a string
cli/daemon/engine/trace2/sqlite/write.go:156 — SQL built from a string
05.26

33 locked dependencies have published vulnerabilities, 3 high or critical

adequate

33 of 1,109 locked dependencies match 48 published advisories in OSV, 3 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
Cargo.lock — rustls 0.19.1: RUSTSEC-2024-0336 (high), fixed in 0.21.11
Cargo.lock — rustls-webpki 0.101.7: GHSA-82j2-j2ch-gfr8 (high), fixed in 0.103.13
Cargo.lock — webpki 0.21.4: GHSA-8qv2-5vq6-g2g7 (high), fixed in 0.22.2
05.65

6 advisories against this project in the last 24 months, 3 high or critical

adequate

The newest was published on 2026-07-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 6 records name encore with nothing tying them to this repository (CVE-2004-1888, CVE-2008-6191, CVE-2014-5127, …).

Evidence
2026-07-29: GHSA-jm2f-2pwf-qfv9 (low), fixed in 1.57.13: Code injection via adversarial doc comments for `encore gen client`
2026-07-29: GHSA-5cq5-fpx7-2wmx (moderate), fixed in 1.57.13: Path traversal in the local object storage emulator
2026-07-29: GHSA-wpvj-6m4r-5v3h (critical), fixed in 1.57.13: Encore CLI daemon exposes localhost-bound development servers to cross-origin browser requests
2026-07-29: GHSA-72fg-v7vh-4q32 (moderate), fixed in 1.57.11: Decimal DoS
2026-07-29: GHSA-8wqj-wmx4-3j23 (high), fixed in 1.57.11: CLI cross-origin WebSocket

Observability & Operations

strong
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 encoredev/encore: 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.