Read 2026-11-03
getagentseal/codeburn: technical due diligence, read from its repository
What Borehole read in getagentseal/codeburn's code and history at f846b63: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:132: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/parser.ts is 6,822 lines, 42× this codebase's median file
adequateThe median source file here is 160 lines. 21 files exceed 1,600 lines, the largest being 6,822. 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.
src/parser.ts:1 — 6,822 lines (42× median) |
src/optimize.ts:1 — 4,482 lines (28× median) |
src/providers/copilot.ts:1 — 3,857 lines (24× median) |
src/main.ts:1 — 3,408 lines (21× median) |
mac/Sources/CodeBurnMenubar/AppStore.swift:1 — 3,391 lines (21× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (app/renderer/lib/cohortStats.test.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
app/renderer/lib/cohortStats.test.ts:82 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| GitHub token, where fakes are usual |
| JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate2 steps pipe a download straight into a shell. 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.
windows/Scripts/provision-linux.sh:7 — download piped into a shell |
14 locked dependencies have published vulnerabilities, 1 high or critical in what ships
adequate14 of 797 locked dependencies match 15 published advisories in OSV, 2 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.
windows/src-tauri/Cargo.lock — zip 9.0.0: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
package-lock.json — zod 3.25.76: GHSA-mrhx-c7xc-m3w5 (high), fixed in 4.6.6 |
package-lock.json — @hono/node-server 1.19.17: GHSA-rmxm-3fg6-px4f (moderate), fixed in 2.1.3 |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 1,388 files for 10 structured logging libraries; 0 matched |
No error reporter is wired in
adequateNothing 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.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on getagentseal/codeburn: 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.