Read 2026-11-07
teamcapybara/capybara: technical due diligence, read from its repository
What Borehole read in teamcapybara/capybara's code and history at 265d2d1: 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 |
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strong7 files still carry code deprecated more than two years ago
adequate7 files were marked deprecated over two years ago and still are, the oldest since Apr 2017. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
lib/capybara/config.rb — deprecated since Apr 2017 |
lib/capybara/helpers.rb — deprecated since Mar 2018 |
lib/capybara/minitest/spec.rb — deprecated since Dec 2018 |
lib/capybara/node/matchers.rb — deprecated since Dec 2018 |
lib/capybara/rspec/matchers.rb — deprecated since Dec 2018 |
Security & Reliability Posture
adequate2 workload settings give a container the host
adequate2 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
docker-compose.yml:4 — privileged or host namespace |
docker-compose.yml:9 — privileged or host namespace |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 282 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 282 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 282 files for 10 structured logging libraries; 0 matched |
One request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 teamcapybara/capybara: 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.