Read 2026-11-03
fastcrw/crw: technical due diligence, read from its repository
What Borehole read in fastcrw/crw's code and history at ac5344a: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:9: The project does not take pull requests
Architecture & Codebase — including AI provenance
adequatecrates/crw-renderer/src/lib.rs is 11,143 lines, 57× this codebase's median file
adequateThe median source file here is 194 lines. 15 files exceed 1,940 lines, the largest being 11,143. 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.
crates/crw-renderer/src/lib.rs:1 — 11,143 lines (57× median) |
crates/crw-renderer/src/cdp.rs:1 — 5,662 lines (29× median) |
crates/crw-core/src/types.rs:1 — 5,515 lines (28× median) |
crates/crw-core/src/config.rs:1 — 5,494 lines (28× median) |
crates/crw-crawl/src/single.rs:1 — 4,097 lines (21× median) |
1 base image floats: no version, or `latest`
adequate1 of 6 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
.clusterfuzzlite/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
adequate19 tests are switched off
adequate19 skip markers across 6 of 109 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
crates/crw-browse/tests/phase2_tools.rs:5 — skipped test |
crates/crw-browse/tests/walking_skeleton.rs:7 — skipped test |
crates/crw-renderer/tests/browser_pool_real_chrome.rs:3 — skipped test |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
.clusterfuzzlite/Dockerfile — runs as root |
Dockerfile — runs as root |
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.
install.sh:4 — download piped into a shell |
11 locked dependencies have published vulnerabilities
adequate11 of 633 locked dependencies match 29 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.
Cargo.lock — rustls 0.23.41: GHSA-2mjx-qc3c-rqvc (moderate), fixed in 0.23.45 |
Cargo.lock — event-listener 5.4.1: RUSTSEC-2026-0221 (unrated), fixed in 5.4.2 |
Cargo.lock — h2 0.4.15: RUSTSEC-2026-0258 (unrated), fixed in 0.4.16 |
2 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-08-09. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 2 records name crw with nothing tying them to this repository (CVE-2026-80547, CVE-2026-80553).
| 2026-08-09: GHSA-5jp3-339h-vxqw (high), fixed in 0.30.0: SSRF via JS-Rendering (CDP) Tiers Bypasses URL Safety Filter in crw Allows Attacker to Read Internal Network Responses via Open Redirect |
| 2026-07-22: GHSA-qq8c-fch4-cxq7 (high), fixed in 0.26.1: Admin and metrics routes are not covered by API key authentication, and CORS defaults to permissive |
Observability & Operations
not assessableNo 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 |
2 of 4 deployed images carry no version, or `latest`
adequate2 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker-compose.yml:135 — image without a version |
docker-compose.yml:185 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on fastcrw/crw: 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.