Borehole · Project · free tier
dandavison/delta
Free reading: not for reliance
5ddd7fa · 2,181 commits · 204 files
Read 2026-10-04

dandavison/delta: technical due diligence, read from its repository

What Borehole read in dandavison/delta's code and history at 5ddd7fa: 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 Posturenot assessable
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong
04.1

Change keeps returning to the same few files

adequate

Five files out of 405 absorb 31% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.

Evidence
README.md — 294 commits touched it
src/cli.rs — 248 commits touched it
src/main.rs — 247 commits touched it
src/paint.rs — 242 commits touched it
src/delta.rs — 213 commits touched it

Security & Reliability Posture

not assessable
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/audit.yml:19 — action pinned by tag
.github/workflows/cd.yml:39 — action pinned by tag
05.26

10 locked dependencies have published vulnerabilities

adequate

10 of 277 locked dependencies match 13 published advisories in OSV. 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 — idna 0.5.0: GHSA-h97m-ww89-6jmq (moderate), fixed in 1.0.0
Cargo.lock — serde_with 3.17.0: GHSA-7gcf-g7xr-8hxj (moderate), fixed in 3.21.0
Cargo.lock — time 0.3.36: GHSA-r6v5-fh4h-64xc (moderate), fixed in 0.3.47

Observability & Operations

not assessable

Not rated: only 4 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on dandavison/delta: 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.