Read 2026-11-03
tracecathq/tracecat: technical due diligence, read from its repository
What Borehole read in tracecathq/tracecat's code and history at 7496784: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: Apache-2.0 → AGPL-3.0 (2024-05-29)packages/tracecat-registry/tracecat_registry/core/ee/__init__.py: 5 files are named as enterprise-edition code
Architecture & Codebase — including AI provenance
strongtracecat/mcp/server.py is 11,322 lines, 82× this codebase's median file
adequateThe median source file here is 138 lines. 54 files exceed 1,380 lines, the largest being 11,322. 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.
tracecat/mcp/server.py:1 — 11,322 lines (82× median) |
frontend/src/lib/hooks.tsx:1 — 7,567 lines (54× median) |
tracecat/db/models.py:1 — 7,421 lines (53× median) |
tracecat/integrations/service.py:1 — 5,295 lines (38× median) |
frontend/src/components/agents/agent-presets-builder.tsx:1 — 4,382 lines (31× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (frontend/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
frontend/playwright.config.ts:11 — test retry |
7% of recent commits change more than 2,000 lines
adequate238 of 3432 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.
| 238 commits over 2,000 lines |
Product & Engineering Maturity
adequate113 direct dependencies in a single manifest
adequatefrontend/package.json declares 113 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.
frontend/package.json — 113 declared |
pyproject.toml — 62 declared |
packages/tracecat-registry/pyproject.toml — 35 declared |
packages/tracecat-benchmark/pyproject.toml — 8 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 1.3.1, is not on the branch this survey read; the newest release on it is 0.53.25. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 1.3.1 |
Security & Reliability Posture
adequate14 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.
| 5 cited: Slack token, where fakes are usual |
3 credential-shaped strings added in the history 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.
| 3 cited: Slack token, where fakes are usual |
2 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.
deployments/postgres/Dockerfile — runs as root |
frontend/Dockerfile — runs as root |
3 SQL statements built from strings
adequate3 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
tracecat/db/locks.py:56 — SQL built from a string |
tracecat/managed_resources/guard.py:94 — SQL built from a string |
tracecat/tables/service.py:627 — SQL built from a string |
1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
tracecat/agent/preset/workflow_references.py:35 — code-executing deserialiser |
TLS certificate checks can be switched off by the user in 4 places
adequate4 places disable certificate verification only when a setting named for it asks: inside a branch on it, such as an `--insecure` flag, or in a client that such a branch picks, or in a probe the service runs against itself. That is an opt-in for self-signed or test servers, not verification switched off. Worth knowing whether production can reach the setting.
packages/tracecat-registry/tracecat_registry/core/email.py:230 — verification off behind an opt-in |
packages/tracecat-registry/tracecat_registry/core/email.py:231 — verification off behind an opt-in |
packages/tracecat-registry/tracecat_registry/core/http.py:658 — verification off behind an opt-in |
1 workload setting give a container the host
adequate1 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
docker-compose.sandbox.yml:31 — privileged or host namespace |
Relicensed: Apache-2.0 → AGPL-3.0 (2024-05-29)
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.
5 files are named as enterprise-edition code
adequateFiles named `.ee.` are, by the common open-core convention, the paid edition's code, usually under a licence that is not open source even where the rest is. What the buyer may do with each part differs.
packages/tracecat-registry/tracecat_registry/core/ee/__init__.py — enterprise-edition file |
packages/tracecat-registry/tracecat_registry/core/ee/durations.py — enterprise-edition file |
packages/tracecat-registry/tracecat_registry/core/ee/tasks.py — enterprise-edition file |
12 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-10-20. 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 12 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 0.53.25. Answer lives in: the release you run, set against each fixed version.
| 2026-10-20: GHSA-9r3g-rq48-gm5p (high), fixed in <1.1.0: SAML authentication bypass via XML Signature Wrapping — identity taken from unvalidated response XML |
| 2026-09-20: GHSA-vrpg-69fg-jc99 (moderate), fixed in >= 1.0.0-rc.2: Custom LLM provider validation could reach restricted network destinations |
| 2026-09-20: GHSA-wfw2-32fr-rc64 (moderate), fixed in >= 1.0.0-beta.52-rc.11: Self-registration could grant read-only organization access in some single-tenant deployments |
| 2026-09-20: GHSA-676v-q2v4-gm7w (moderate), fixed in >= 1.0.0-beta.52-rc.24: Workflow execution errors could expose referenced secret values to workspace viewers |
| 2026-09-20: GHSA-gcp8-xp59-qqvp (high), fixed in >= 1.0.0-beta.51-rc.14: Organization admins could assign themselves owner-only permissions |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 5,626 files for 10 structured logging libraries; 0 matched |
1 of 11 deployed images carry no version, or `latest`
adequate1 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.lite.yml:38 — 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 tracecathq/tracecat: 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.