Read 2026-10-23
pythagora-io/gpt-pilot: technical due diligence, read from its repository
What Borehole read in pythagora-io/gpt-pilot's code and history at 9b763fd: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
README.md:16: The repository says it is no longer maintained- Releases are cut from another branch than the one surveyed
LICENSE:1: The licence is FSL-1.1-MIT: source available, not open sourceLICENSE: Relicensed: Apache-2.0 → MIT (2023-08-28) → FSL-1.1-MIT (2024-05-28)
Architecture & Codebase — including AI provenance
strongcore/db/models/project_state.py is 1,079 lines, 18× this codebase's median file
adequateThe median source file here is 59 lines. 2 files exceed 1,000 lines, the largest being 1,079. 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.
core/db/models/project_state.py:1 — 1,079 lines (18× median) |
core/state/state_manager.py:1 — 1,047 lines (17× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate5% of bug fixes add or change a test
adequateOf 288 fixes in the last 24 months, 13 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.
| 13 of 288 |
The repository says it is no longer maintained
adequateIts own README says so on line 16: "This repository is **no longer actively maintained**, which is why the malicious commit went unnoticed for an". Everything else in this report describes code its maintainers have said they will not carry forward. A buyer inherits the maintenance.
README.md:16 — This repository is **no longer actively maintained**, which is why the malicious commit went unnoticed for an |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 0.2.13, is not on the branch this survey read. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 0.2.13 |
Security & Reliability Posture
adequate224 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
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 |
4 environment files are committed
adequatecore/templates/tree/node_express_mongoose/.env, core/templates/tree/react_express/.env, core/templates/tree/vite_react/server/.env and more are 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.
core/templates/tree/node_express_mongoose/.env — committed environment file |
core/templates/tree/react_express/.env — committed environment file |
core/templates/tree/vite_react/server/.env — committed environment file |
The build runs third-party code it does not pin
adequate2 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; 1 step pipes 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/cloud-staging-build.yaml:127 — action pinned by tag |
.github/workflows/cloud-staging-build.yaml:134 — action pinned by tag |
cloud/setup-dependencies.sh:59 — download piped into a shell |
The licence is FSL-1.1-MIT: source available, not open source
adequateLICENSE grants FSL-1.1-MIT: source available, not open source; a competing commercial product or service is not allowed; each version becomes MIT two years after its release. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.
LICENSE:1 — 110 lines, FSL-1.1-MIT |
Relicensed: Apache-2.0 → MIT (2023-08-28) → FSL-1.1-MIT (2024-05-28)
adequateThe root licence changed 2 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.
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on pythagora-io/gpt-pilot: 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.