Read 2026-10-05
baristaze/swe_guidelines: technical due diligence, read from its repository
What Borehole read in baristaze/swe_guidelines's code and history at f0f8348: 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 | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongscaffold/acme_root/clients/typescript/src/schema.d.ts is 4,169 lines, 52× this codebase's median file
adequateThe median source file here is 80 lines. 6 files exceed 1,000 lines, the largest being 4,169. 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.
scaffold/acme_root/clients/typescript/src/schema.d.ts:1 — 4,169 lines (52× median) |
checkers/src/arch_check/rules/storage.py:1 — 1,349 lines (16× median) |
scaffold/acme_root/om/src/acme/om/tenancy/storage/impl/postgres.py:1 — 1,133 lines (14× median) |
checkers/src/arch_check/rules/async_.py:1 — 1,077 lines (13× median) |
checkers/src/arch_check/rules/delivery.py:1 — 1,036 lines (12× median) |
Engineering Process & SDLC Maturity
adequate16% of recent commits change more than 2,000 lines
adequate23 of 146 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 23 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong2 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 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.
scaffold/acme_root/om/src/acme/om/storage/logins.py:70 — SQL built from a string |
scaffold/acme_root/om/src/acme/om/storage/impl/pg_base.py:178 — SQL built from a string |
1 locked dependency has published vulnerabilities
adequate1 of 394 locked dependencies match 1 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.
scaffold/acme_root/uv.lock — pyjwt 2.14.0: GHSA-42vr-xj54-vc7v (moderate), fixed in 2.15.0 |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on baristaze/swe_guidelines: 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.