Read 2026-10-23
tyktechnologies/tyk: technical due diligence, read from its repository
What Borehole read in tyktechnologies/tyk's code and history at f05509e: 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 | 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
ee/LICENSE-EE.md: Part of the code is under a separate licence: ee/
Architecture & Codebase — including AI provenance
strongcoprocess/bindings/java/CoprocessSessionState.java is 7,384 lines, 53× this codebase's median file
adequateThe median source file here is 139 lines. 21 files exceed 1,390 lines, the largest being 7,384. 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.
coprocess/bindings/java/CoprocessSessionState.java:1 — 7,384 lines (53× median) |
coprocess/bindings/cpp/coprocess_session_state.pb.cc:1 — 4,618 lines (33× median) |
gateway/api.go:1 — 3,823 lines (27× median) |
gateway/api_definition.go:1 — 2,815 lines (20× median) |
coprocess/bindings/java/CoprocessMiniRequestObject.java:1 — 2,751 lines (19× median) |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate31 of 550 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.
| 31 commits over 2,000 lines |
Product & Engineering Maturity
adequate115 direct dependencies in a single manifest
adequatego.mod declares 115 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.
go.mod — 115 declared |
15 files still carry code deprecated more than two years ago
adequate15 files were marked deprecated over two years ago and still are, the oldest since Nov 2019. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
apidef/api_definitions.go — deprecated since Nov 2019 |
config/config.go — deprecated since Dec 2019 |
user/session.go — deprecated since Sep 2020 |
apidef/oas/upstream.go — deprecated since Apr 2023 |
coprocess/coprocess_session_state.pb.go — deprecated since Jun 2023 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v5.15.1, is not on the branch this survey read; the newest release on it is v2.9.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v5.15.1 |
Security & Reliability Posture
adequate6 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. 1 other match set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| private key block, where fakes are usual |
| 4 cited: JWT, 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.
Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate7 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; 1 step pipes 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-tests.yml:32 — action pinned by tag |
.github/workflows/drift-check.yml:9 — action pinned by tag |
.github/workflows/lint-swagger.yml:71 — download piped into a shell |
5 outbound calls can wait forever
adequate5 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
gateway/mw_external_oauth.go:369 — outbound call without a timeout |
gateway/service_discovery.go:73 — outbound call without a timeout |
gateway/service_discovery.go:79 — outbound call without a timeout |
1 locked dependency has published vulnerabilities, 1 high or critical
adequate1 of 614 locked dependencies match 2 published advisories in OSV, 1 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.
go.mod — github.com/docker/docker v28.5.2+incompatible: GO-2026-4887 (high) |
Part of the code is under a separate licence: ee/
adequateA directory named for a paid edition carries its own licence. That code is usually not open source even where the rest is; what the buyer may do with each part differs.
ee/LICENSE-EE.md — licence: LicenseRef-EULA |
Observability & Operations
strongNo 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 tyktechnologies/tyk: 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.