Read 2026-10-04
lukevella/rallly: technical due diligence, read from its repository
What Borehole read in lukevella/rallly's code and history at de955de: 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 | 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
strongpackages/ui/src/event-calendar/event-calendar.tsx is 1,745 lines, 31× this codebase's median file
adequateThe median source file here is 56 lines. 7 files exceed 1,000 lines, the largest being 1,745. 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.
packages/ui/src/event-calendar/event-calendar.tsx:1 — 1,745 lines (31× median) |
packages/database/prisma/seed/data.ts:1 — 1,642 lines (29× median) |
apps/web/src/trpc/routers/polls.ts:1 — 1,595 lines (28× median) |
packages/ui/src/event-calendar/event-calendar-time-grid.tsx:1 — 1,267 lines (22× median) |
packages/ui/src/event-calendar/event-calendar-month-view.tsx:1 — 1,154 lines (20× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate85 direct dependencies in a single manifest
adequateapps/web/package.json declares 85 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.
apps/web/package.json — 85 declared |
apps/landing/package.json — 31 declared |
packages/ui/package.json — 31 declared |
packages/emails/package.json — 13 declared |
13% of bug fixes add or change a test
adequateOf 215 fixes in the last 24 months, 27 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.
| 27 of 215 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v4.15.3, is not on the branch this survey read; the newest release on it is v4.15.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.15.3 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate6 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/docker-image.yml:63 — action pinned by tag |
.github/workflows/docker-image.yml:75 — action pinned by tag |
52 locked dependencies have published vulnerabilities, 50 high or critical in what ships
adequate52 of 2,563 locked dependencies match 148 published advisories in OSV, 89 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 — fast-xml-parser 5.3.4: GHSA-m7jm-9gc2-mpf2 (critical), fixed in 5.3.5 |
pnpm-lock.yaml — basic-ftp 5.1.0: GHSA-5rq4-664w-9x2c (critical), fixed in 5.2.0; a development dependency |
pnpm-lock.yaml — @tiptap/core 3.27.3: GHSA-j95f-988m-3j2f (high), fixed in 3.30.5 |
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
apps/landing/next.config.ts:19 — source maps in a production build |
apps/web/next.config.ts:24 — source maps in a production build |
15 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-09-16. 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 10 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 4.15.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-16: CVE-2026-92565 (moderate): Rallly before 4.15.0 contains an information disclosure vulnerability in the polls.get tRPC procedure that returns scheduled-event invitee names and email addre |
| 2026-09-09: GHSA-jprp-6gw6-jwcr (moderate), fixed in 4.12.0: Unauthenticated Access to Deleted Poll Data via Public API |
| 2026-08-03: GHSA-34w3-569j-j947 (moderate), fixed in 4.12.0: Rallly: a space administrator can remove or demote the space owner, permanently locking the owner out of their own space |
| 2026-04-17: CVE-2026-6493 (low): A flaw has been found in lukevella rallly up to 4.7.4. This affects an unknown function of the file apps/web/src/app/[locale]/(auth)/reset-password/components/r |
| 2025-11-28: GHSA-65wg-8xgw-f3fg (moderate), fixed in >= 4.5.6: Information Disclosure in Participant API Leaks Names and Emails Despite Pro Privacy Settings |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on lukevella/rallly: 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.