Read 2026-11-03
corebunch/instatic: technical due diligence, read from its repository
What Borehole read in corebunch/instatic's code and history at 2e6b426: 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 | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongserver/db/migrations-sqlite.ts is 1,530 lines, 13× this codebase's median file
adequateThe median source file here is 114 lines. 2 files exceed 1,140 lines, the largest being 1,530. 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.
server/db/migrations-sqlite.ts:1 — 1,530 lines (13× median) |
server/db/migrations-pg.ts:1 — 1,374 lines (12× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (playwright.config.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.
playwright.config.ts:19 — test retry |
9% of recent commits change more than 2,000 lines
adequate103 of 1091 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.
| 103 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strong85 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
package.json:6 — >=1.4.0 <1.5.0 |
package.json:63 — ^6.20.1 |
package.json:64 — ^6.3.1 |
package.json:65 — ^6.4.11 |
package.json:66 — ^6.2.5 |
The build runs third-party code it does not pin
adequate5 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.
.github/workflows/ci.yml:28 — action pinned by tag |
.github/workflows/release.yml:55 — action pinned by tag |
10 places insert HTML from a variable without sanitising it
adequate10 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
server/publish/holeRuntime.ts:28 — HTML from a variable |
server/publish/holeRuntime.ts:41 — HTML from a variable |
server/publish/loopRuntime.ts:70 — HTML from a variable |
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
vendor/pixel-art-icons — 423 tracked files, no licence file |
3 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-11-03. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.0.21. Answer lives in: the release you run, set against each fixed version.
| 2026-11-03: GHSA-x5cc-8486-8qqx (moderate), fixed in 0.0.21: Authorization Bypass in the AI/MCP Content Read Tools Allows Reading Any User's Private Drafts and System-Table Rows |
| 2026-11-03: GHSA-m425-wmrc-4v4v (high), fixed in 0.0.21: Authorization Bypass in PATCH /admin/api/cms/data/rows/:id/author Allows Reading Any System-Table Row and Reassigning Its Author |
| 2026-11-03: CVE-2026-121458 (high): Instatic before 0.0.21 contains a missing authorization vulnerability in its AI/MCP content read tools that allows low-privileged authenticated users with ai.ch |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 2,800 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 2,800 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 2,800 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 corebunch/instatic: 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.