Read 2026-10-23
vectordotdev/vector: technical due diligence, read from its repository
What Borehole read in vectordotdev/vector's code and history at 23fa5a9: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: Apache-2.0 → MPL-2.0 (2020-09-03)AI_POLICY.md:1: states a policy on AI-generated contributionsSECURITY.md:216: names OpenSSF
Architecture & Codebase — including AI provenance
strongsrc/sources/splunk_hec/mod.rs is 4,158 lines, 27× this codebase's median file
adequateThe median source file here is 149 lines. 30 files exceed 1,490 lines, the largest being 4,158. 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.
src/sources/splunk_hec/mod.rs:1 — 4,158 lines (27× median) |
src/sources/datadog_agent/tests.rs:1 — 3,225 lines (21× median) |
src/sources/file.rs:1 — 2,644 lines (17× median) |
src/sources/kafka.rs:1 — 2,485 lines (16× median) |
src/sources/opentelemetry/tests.rs:1 — 2,405 lines (16× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate14% of bug fixes add or change a test
adequateOf 657 fixes in the last 24 months, 89 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.
| 89 of 657 |
5 files still carry code deprecated more than two years ago
adequate5 files were marked deprecated over two years ago and still are, the oldest since Jul 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
lib/vector-config-macros/src/ast/container.rs — deprecated since Jul 2022 |
lib/vector-config-macros/src/ast/field.rs — deprecated since Jul 2022 |
lib/vector-config-macros/src/ast/variant.rs — deprecated since Jul 2022 |
lib/vector-core/src/sink.rs — deprecated since Jun 2023 |
lib/vector-core/src/config/global_options.rs — deprecated since Nov 2024 |
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: JWT, where fakes are usual |
6 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.
distribution/docker/alpine/Dockerfile — runs as root |
distribution/docker/debian/Dockerfile — runs as root |
distribution/docker/distroless-libc/Dockerfile — runs as root |
distribution/docker/distroless-static/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.
scripts/environment/prepare.sh:136 — download piped into a shell |
3 of 3 Kubernetes workloads declare no resource limits
adequate3 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
distribution/kubernetes/vector-agent/daemonset.yaml — workload with no limits |
distribution/kubernetes/vector-aggregator/statefulset.yaml — workload with no limits |
distribution/kubernetes/vector-stateless-aggregator/deployment.yaml — workload with no limits |
12 locked dependencies have published vulnerabilities
adequate12 of 1,655 locked dependencies match 16 published advisories in OSV. 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 — rsa 0.9.10: RUSTSEC-2023-0071 (moderate) |
website/yarn.lock — postcss-selector-parser 6.0.10: GHSA-rj75-hqrm-r3gf (moderate), fixed in 7.1.6 |
Cargo.lock — ctutils 0.4.2: RUSTSEC-2026-0385 (unrated), fixed in 0.4.4 |
6 places insert HTML from a variable without sanitising it
adequate6 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.
lib/vector-vrl/web-playground/public/index.js:291 — HTML from a variable |
website/assets/js/below.js:72 — HTML from a variable |
website/assets/js/below.js:87 — HTML from a variable |
Relicensed: Apache-2.0 → MPL-2.0 (2020-09-03)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
3 advisories against this project in the last 24 months, 3 high or critical
adequateThe newest was published on 2026-07-14. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: its keyword search for 'vector' is too broad to read whole (28,532 records).
| 2026-07-14: GHSA-qp6f-fpfx-4gg6 (high), fixed in 0.57.0: Unauthenticated denial of service in the `logstash` source via nested compressed frames (stack exhaustion and decompression amplification). |
| 2026-07-14: GHSA-rrfg-9487-mhp6 (high), fixed in 0.57.0: Unauthenticated denial of service in the `logstash` source via unbounded memory allocation. |
| 2026-07-14: GHSA-6342-xwvw-c637 (critical), fixed in v0.57.0: Arbitrary file write in the file sink via templated path (path traversal). |
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 |
2 of 2 deployments run a single replica
adequate2 deployments set `replicas: 1`, and nothing (an autoscaler, a disruption budget) adds more. Every deploy and every node drain is downtime, and the availability the buyer inherits has a ceiling.
distribution/kubernetes/vector-aggregator/statefulset.yaml — replicas: 1 |
distribution/kubernetes/vector-stateless-aggregator/deployment.yaml — replicas: 1 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on vectordotdev/vector: 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.