Read 2026-10-23
hyperdxio/hyperdx: technical due diligence, read from its repository
What Borehole read in hyperdxio/hyperdx's code and history at 0b753cc: 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
AGENTS.md:281: states a policy on AI-generated contributionsREADME.md:94: names CNCF
Architecture & Codebase — including AI provenance
strongpackages/api/src/routers/external-api/v2/dashboards.ts is 3,752 lines, 27× this codebase's median file
adequateThe median source file here is 136 lines. 25 files exceed 1,360 lines, the largest being 3,752. 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/api/src/routers/external-api/v2/dashboards.ts:1 — 3,752 lines (27× median) |
packages/app/src/DBDashboardPage.tsx:1 — 3,579 lines (26× median) |
packages/common-utils/src/types.ts:1 — 3,456 lines (25× median) |
packages/common-utils/src/core/renderChartConfig.ts:1 — 3,394 lines (24× median) |
packages/common-utils/src/core/metadata.ts:1 — 3,338 lines (24× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateAPI v1 and v2 have been served together for 18 months
adequatev2 first appeared in Apr 2025, and v1 is still in the code 18 months later. Two versions mean two surfaces to secure, document and support. Ask who still calls the old one, and whether retiring it is planned.
packages/api/src/api-app.ts — v1 since Nov 2023 |
packages/api/src/api-app.ts — v2 since Apr 2025 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, hyperdx@1.10.1, is not on the branch this survey read; the newest release on it is hyperdx@1.10.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag hyperdx@1.10.1 |
Security & Reliability Posture
adequate8 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 |
| 4 cited: Slack token, where fakes are usual |
None 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 2,256 tracked files; 0 present |
1 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.
docker/hostmetrics/Dockerfile — runs as root |
1 environment file is committed
adequate.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
.env — committed environment file |
The build runs third-party code it does not pin
adequate12 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-code-review.yml:217 — action pinned by tag |
.github/workflows/claude-code-review.yml:347 — action pinned by tag |
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
packages/cli/src/utils/editor.ts:161 — command run through a shell |
packages/cli/src/utils/editor.ts:190 — command run through a shell |
95 locked dependencies have published vulnerabilities, 97 high or critical
adequate95 of 2,908 locked dependencies match 187 published advisories in OSV, 97 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
3 advisories 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. Whether 1 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 1.10.0. Answer lives in: the release you run, set against each fixed version.
| 2026-08-28: CVE-2026-82279 (high): HyperDX through 1.10.1 fails to enforce role-based access controls in team management endpoints, allowing any team member to perform administrative actions. Att |
| 2026-07-20: CVE-2026-63730 (moderate): HyperDX before 2.31.0 contains a server-side request forgery vulnerability that allows authenticated team members to direct the server to make requests to arbit |
| 2026-07-20: CVE-2026-63731 (moderate): HyperDX before 2.31.0 contains a server-side request forgery vulnerability that allows authenticated team members to direct the server to arbitrary internal des |
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 hyperdxio/hyperdx: 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.