Read 2026-10-23
heygen-com/hyperframes: technical due diligence, read from its repository
What Borehole read in heygen-com/hyperframes's code and history at fb2f7c1: 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 |
What the repository says
CONTRIBUTING.md:249: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongregistry/blocks/cuboid-carousel/assets/cuboid-motion.js is 12,313 lines, 100× this codebase's median file
adequateThe median source file here is 122 lines. 42 files exceed 1,220 lines, the largest being 12,313. 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.
registry/blocks/cuboid-carousel/assets/cuboid-motion.js:1 — 12,313 lines (100× median) |
packages/core/src/runtime/init.ts:1 — 5,665 lines (46× median) |
packages/producer/src/services/renderOrchestrator.ts:1 — 5,369 lines (44× median) |
packages/engine/src/services/frameCapture.ts:1 — 5,119 lines (41× median) |
packages/core/src/runtime/colorGrading.ts:1 — 4,245 lines (34× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/engine/src/services/videoFrameExtractor.test.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/engine/src/services/videoFrameExtractor.test.ts:542 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate2 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| AWS access key, where fakes are usual |
| JWT, where fakes are usual |
2 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.
packages/aws-lambda/image/Dockerfile — runs as root |
packages/gcp-cloud-run/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.
packages/gcp-cloud-run/Dockerfile:103 — download piped into a shell |
72 places insert HTML from a variable without sanitising it
adequate72 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.
packages/cli/src/commands/motionShot.ts:725 — HTML from a variable |
packages/cli/src/commands/motionShot.ts:766 — HTML from a variable |
packages/cli/src/media-use/lib/svg-sanitize.mjs:16 — HTML from a variable |
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
docs/public/catalog/vendor/three-modules.json — 1 tracked files, no licence file |
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 7,479 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 heygen-com/hyperframes: 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.