Read 2026-11-03
tracer-cloud/opensre: technical due diligence, read from its repository
What Borehole read in tracer-cloud/opensre's code and history at 9883902: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
.github/PULL_REQUEST_TEMPLATE.md:20: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongintegrations/_catalog_impl.py is 2,231 lines, 22× this codebase's median file
adequateThe median source file here is 99 lines. 12 files exceed 1,000 lines, the largest being 2,231. 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.
integrations/_catalog_impl.py:1 — 2,231 lines (22× median) |
config/constants/__init__.py:1 — 1,781 lines (17× median) |
install.sh:1 — 1,694 lines (17× median) |
core/agent_harness/turns/action_driver.py:1 — 1,692 lines (17× median) |
integrations/github/mcp.py:1 — 1,487 lines (15× median) |
Engineering Process & SDLC Maturity
adequate6% of recent commits change more than 2,000 lines
adequate211 of 3575 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.
| 211 commits over 2,000 lines |
Product & Engineering Maturity
strongNode.js 25 is past end of life
adequateThe code is pinned to Node.js 25 (end of life 2026-06-01). None of these receives security fixes any more; the first stopped on 2026-06-01. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
.tool-versions — Node.js 25, end of life 2026-06-01 |
Security & Reliability Posture
adequate34 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.
| AWS access key, where fakes are usual |
| 4 cited: GitHub token, where fakes are usual |
The build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 9 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-labels-windows.yml:66 — action pinned by tag |
.github/workflows/release.yml:674 — download piped into a shell |
10 SQL statements built from strings
adequate10 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
gateway/core/storage/session/legacy_sqlite.py:53 — SQL built from a string |
infrastructure/scheduling/scheduler/storage/run_store.py:571 — SQL built from a string |
infrastructure/scheduling/scheduler/storage/run_store.py:592 — 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.
core/agent_harness/prompts/skills/catalog/schema.py:109 — code-executing deserialiser |
1 advisory against this project in the last 24 months, 1 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 1 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 2026.6.26. Answer lives in: the release you run, set against each fixed version.
| 2026-10-20: CVE-2026-109444 (critical): OpenSRE through 0.1.2026.10.19 contains an approval gate bypass vulnerability that allows attackers to execute shell_run commands without confirmation because t |
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 3,954 files for 10 structured logging libraries; 0 matched |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on tracer-cloud/opensre: 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.