Borehole · Project · free tier
dbos-inc/dbos-transact-py
Free reading: not for reliance
718d066 · 651 commits · 124 files
Read 2026-10-28

dbos-inc/dbos-transact-py: technical due diligence, read from its repository

What Borehole read in dbos-inc/dbos-transact-py's code and history at 718d066: 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 Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

dbos/_sys_db.py is 6,967 lines, 25× this codebase's median file

adequate

The median source file here is 275 lines. 3 files exceed 2,750 lines, the largest being 6,967. 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
dbos/_sys_db.py:1 — 6,967 lines (25× median)
dbos/_dbos.py:1 — 4,434 lines (16× median)
dbos/_core.py:1 — 3,483 lines (12× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

strong
05.21

9 shell commands built from strings

adequate

9 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

Evidence
dbos/_docker_pg_helper.py:85 — command run through a shell
dbos/_docker_pg_helper.py:101 — command run through a shell
dbos/_docker_pg_helper.py:118 — command run through a shell
05.22

1 deserialiser that can run code

adequate

1 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

Evidence
dbos/_serialization.py:108 — code-executing deserialiser

Observability & Operations

not assessable

Not rated: only 5 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 dbos-inc/dbos-transact-py: 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.