Read 2026-11-03
hypit-ai/hypit: technical due diligence, read from its repository
What Borehole read in hypit-ai/hypit's code and history at 0762c6b: 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 | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE:1: The licence is Apache-2.0 with a commercial-licence condition: source available, not open source
Architecture & Codebase — including AI provenance
strongpackages/composition/src/track.ts is 1,457 lines, 17× this codebase's median file
adequateThe median source file here is 84 lines. 10 files exceed 1,000 lines, the largest being 1,457. 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/composition/src/track.ts:1 — 1,457 lines (17× median) |
packages/media-local/src/execute.ts:1 — 1,381 lines (16× median) |
packages/runtime-local/src/config.ts:1 — 1,265 lines (15× median) |
packages/html-program/src/text.ts:1 — 1,189 lines (14× median) |
packages/caption-fine/src/render.ts:1 — 1,163 lines (13× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate103 of 1228 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
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 1,704 tracked files; 0 present |
25 locked dependencies have published vulnerabilities, 48 high or critical in what ships
adequate25 of 493 locked dependencies match 110 published advisories in OSV, 51 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.
packages/yt-dlp/runtime/uv.lock — brotli 1.2.0: GHSA-9v8h-qqgm-4m35 (critical), fixed in 1.2.1 |
packages/yt-dlp/runtime/uv.lock — brotlicffi 1.2.0.2: GHSA-9v8h-qqgm-4m35 (critical), fixed in 1.2.1.0 |
packages/provider-whisperx-local/runtime/uv.lock — certifi 2026.7.22: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
The licence is Apache-2.0 with a commercial-licence condition: source available, not open source
adequateLICENSE grants Apache-2.0 with a commercial-licence condition: source available, not open source; some uses need a commercial licence from the licensor. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 26 lines, Apache-2.0 AND LicenseRef-Terms-CommercialLicence |
Observability & Operations
adequateNo 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 1,469 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 hypit-ai/hypit: 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.