Read 2026-10-23
juspay/hyperswitch: technical due diligence, read from its repository
What Borehole read in juspay/hyperswitch's code and history at 076a191: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| 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
adequatecrates/router/src/core/payments.rs is 18,337 lines, 254× this codebase's median file
adequateThe median source file here is 72 lines. 240 files exceed 1,000 lines, the largest being 18,337. 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.
crates/router/src/core/payments.rs:1 — 18,337 lines (254× median) |
crates/api_models/src/payments.rs:1 — 15,281 lines (212× median) |
crates/hyperswitch_connectors/src/default_implementations.rs:1 — 13,857 lines (192× median) |
crates/common_enums/src/enums.rs:1 — 12,644 lines (175× median) |
crates/router/src/core/unified_connector_service/transformers.rs:1 — 11,504 lines (159× median) |
2 base images float: no version, or `latest`
adequate2 of 5 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
loadtest/Dockerfile:1 — base image without a version |
loadtest/Dockerfile:7 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate15% of bug fixes add or change a test
adequateOf 1130 fixes in the last 24 months, 175 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.
| 175 of 1130 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.128.0, is not on the branch this survey read; the newest release on it is v1.108.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.128.0 |
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.
| 2 cited: private key block, where fakes are usual |
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.
loadtest/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate10 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; 2 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.
.github/workflows/CI-pr.yml:49 — action pinned by tag |
.github/workflows/CI-pr.yml:91 — action pinned by tag |
INSTALL_dependencies.sh:152 — download piped into a shell |
73 locked dependencies have published vulnerabilities, 24 high or critical
adequate73 of 1,121 locked dependencies match 103 published advisories in OSV, 24 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.
Cargo.lock — lettre 0.11.16: GHSA-4pj9-g833-qx53 (critical), fixed in 0.11.22 |
Cargo.lock — traitobject 0.1.1: GHSA-pp8r-vv2j-9j5v (critical) |
Cargo.lock — typemap 0.3.3: GHSA-vfv3-9w6v-23jp (critical) |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
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 |
28 of 46 deployed images carry no version, or `latest`
adequate28 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker-compose.yml:28 — image without a version |
docker-compose.yml:94 — image without a version |
docker-compose-development.yml:186 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on juspay/hyperswitch: 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.