Read 2026-11-03
parseablehq/parseable: technical due diligence, read from its repository
What Borehole read in parseablehq/parseable's code and history at 335835a: 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
README.md:32: The repository says it is feature-complete, in maintenance mode, or needs maintainersLICENSE: Relicensed: Apache-2.0 → AGPL-3.0 (2022-05-10)
Architecture & Codebase — including AI provenance
adequatesrc/parseable/streams.rs is 4,264 lines, 14× this codebase's median file
adequateThe median source file here is 301 lines. 1 file exceed 3,010 lines, the largest being 4,264. 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/parseable/streams.rs:1 — 4,264 lines (14× median) |
1 base image floats: no version, or `latest`
adequate1 of 2 `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.
Dockerfile:29 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateThe repository says it is feature-complete, in maintenance mode, or needs maintainers
adequateIts own README says so on line 32: "…://www.parseable.com/docs/features): Parseable is feature complete with alerting, dashboards, anomaly detection, APM, a". New features are not planned, or the project is asking for maintainers. Ask who will carry it forward.
README.md:32 — …://www.parseable.com/docs/features): Parseable is feature complete with alerting, dashboards, anomaly detection, APM, a |
Security & Reliability Posture
adequateNone 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 221 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.
Dockerfile — runs as root |
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/build-push-edge-debug.yaml:21 — action pinned by tag |
.github/workflows/build-push-edge-debug.yaml:26 — action pinned by tag |
19 locked dependencies have published vulnerabilities
adequate19 of 694 locked dependencies match 35 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 — block-buffer 0.12.0: GHSA-qwgh-2vcv-g2f7 (moderate) |
Cargo.lock — anyhow 1.0.100: RUSTSEC-2026-0190 (unrated), fixed in 1.0.103 |
Cargo.lock — crossbeam-epoch 0.9.18: RUSTSEC-2026-0204 (unrated), fixed in 0.9.20 |
Relicensed: Apache-2.0 → AGPL-3.0 (2022-05-10)
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.
7 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-08-15. 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: 3 records name parseable with nothing tying them to this repository (CVE-2026-110599, CVE-2026-47763, CVE-2026-74464).
| 2026-08-15: GHSA-64vg-fp53-frjx (moderate), fixed in 3.0.0: Server-Side Request Forgery via alert notification target endpoint (reachable by editor/writer) |
| 2026-08-15: GHSA-q8xx-r33r-6mwv (high), fixed in 3.0.0: Path traversal: authenticated arbitrary file write/delete via unvalidated `stream_name` in the Filters API (LocalFS) |
| 2026-08-15: GHSA-2qqm-w7v3-5hr6 (moderate), fixed in 3.0.0: SSRF via webhook target endpoint reachable to Editor/Writer roles (alert delivery) |
| 2026-08-15: GHSA-2x76-24x6-g2xm (high), fixed in 3.0.0: Alert targets allow authenticated users to trigger server-side POST requests to arbitrary URLs |
| 2026-08-15: GHSA-mh89-vfm3-c9q6 (moderate), fixed in 3.0.0: OIDC logout open redirect allows unauthenticated external users to bounce victims to arbitrary domains |
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 |
2 of 6 deployed images carry no version, or `latest`
adequate2 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-test-with-kafka.yaml:131 — image without a version |
docker-compose-test-with-kafka.yaml:99 — 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 parseablehq/parseable: 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.