Read 2026-11-03
oss-review-toolkit/ort: technical due diligence, read from its repository
What Borehole read in oss-review-toolkit/ort's code and history at a88c5b6: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
AI_POLICY.md:1: states a policy on AI-generated contributionsREADME.md:9: names OpenSSFREADME.md:174: names Linux Foundation.gitmodules:1: 5 submodule(s) this survey does not read: plugins/package-managers/python/src/funTest/assets/projects/external/example-python-flask, plugins/package-managers/python/src/funTest/assets/projects/external/spdx-tools-python, plugins/package-managers/stack/src/funTest/assets/projects/external/quickcheck-state-machine
Architecture & Codebase — including AI provenance
strongintegrations/completions/ort-completion.zsh is 1,609 lines, 20× this codebase's median file
adequateThe median source file here is 80 lines. 4 files exceed 1,000 lines, the largest being 1,609. 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/completions/ort-completion.zsh:1 — 1,609 lines (20× median) |
integrations/completions/ort-completion.bash:1 — 1,604 lines (20× median) |
plugins/reporters/web-app-template/src/models/WebAppEvaluatedModel.ts:1 — 1,151 lines (14× median) |
plugins/scanners/fossid/src/main/kotlin/FossId.kt:1 — 1,106 lines (13× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 environment file is committed
adequate.env.versions is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
.env.versions — committed environment file |
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.
Dockerfile:165 — download piped into a shell |
38 locked dependencies have published vulnerabilities, 25 high or critical in what ships
adequate38 of 1,417 locked dependencies match 122 published advisories in OSV, 57 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.
website/package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8; reached only by the build |
website/package-lock.json — tinypool 1.1.0: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; reached only by the build |
website/package-lock.json — browserslist 4.28.1: GHSA-73wf-gq98-2v4g (high), fixed in 4.28.7 |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-09-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. 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 97.3.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-15: GHSA-22w4-pvvm-9g57 (moderate): Host-only authenticator cache can forward credentials across services on the same host |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on oss-review-toolkit/ort: 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.