Read 2026-10-23
rybbit-io/rybbit: technical due diligence, read from its repository
What Borehole read in rybbit-io/rybbit's code and history at 5b8a888: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongserver/public/script-full.js is 1,824 lines, 16× this codebase's median file
adequateThe median source file here is 108 lines. 5 files exceed 1,080 lines, the largest being 1,824. 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/public/script-full.js:1 — 1,824 lines (16× median) |
client/src/app/[site]/dashboards/examples.ts:1 — 1,655 lines (15× median) |
server/src/services/tracker/const.ts:1 — 1,351 lines (12× median) |
client/src/app/[site]/experiments/components/CreateExperimentWizard.tsx:1 — 1,214 lines (11× median) |
server/src/services/tracker/botBlocking/anomalyScorer.ts:1 — 1,199 lines (11× median) |
Engineering Process & SDLC Maturity
adequateAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 2,770 tracked files |
5% of recent commits change more than 2,000 lines
adequate127 of 2446 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.
| 127 commits over 2,000 lines |
Product & Engineering Maturity
adequate86 direct dependencies in a single manifest
adequateclient/package.json declares 86 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
client/package.json — 86 declared |
server/package.json — 45 declared |
17% of bug fixes add or change a test
adequateOf 236 fixes in the last 24 months, 40 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 40 of 236 |
2 jobs are each done by more than one library
adequateWithin a single package: dates: date-fns, luxon; state management: jotai, zustand. Each duplicate is bundle size, two ways of doing the same thing in one codebase, and two upgrade paths to maintain. It is usually the residue of a migration that stopped halfway.
client/package.json — several libraries per job |
server/package.json — several libraries per job |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v2.9.2, is not on the branch this survey read; the newest release on it is v2.9.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.9.2 |
Security & Reliability Posture
adequate1 Dockerfile runs 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.
server/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 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/claude.yml:35 — action pinned by tag |
.github/workflows/docker-publish.yml:34 — action pinned by tag |
44 locked dependencies have published vulnerabilities, 61 high or critical in what ships
adequate44 of 1,484 locked dependencies match 131 published advisories in OSV, 66 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.
pnpm-lock.yaml — basic-ftp 5.1.0: GHSA-5rq4-664w-9x2c (critical), fixed in 5.2.0 |
pnpm-lock.yaml — fast-xml-parser 5.2.5: GHSA-m7jm-9gc2-mpf2 (critical), fixed in 5.3.5 |
pnpm-lock.yaml — next 16.2.6: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
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.
client/src/app/[site]/globe/2d/hooks/useOpenLayersTimelineLayer.ts:284 — HTML from a variable |
client/src/app/[site]/globe/2d/hooks/useOpenLayersTimelineLayer.ts:298 — HTML from a variable |
client/src/app/[site]/globe/2d/hooks/useOpenLayersTimelineLayer.ts:393 — HTML from a variable |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-28. 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.
| 2026-08-28: CVE-2026-82287 (high): Rybbit before 2.7.0 contains a CORS misconfiguration vulnerability that allows attackers to bypass origin restrictions by reflecting any request origin in Acces |
Observability & Operations
strongNo 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 rybbit-io/rybbit: 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.