Read 2026-11-03
pyspur-dev/pyspur: technical due diligence, read from its repository
What Borehole read in pyspur-dev/pyspur's code and history at 97b9856: 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
LICENSE: Relicensed: Apache-2.0 with additional terms → Apache-2.0 with a branding condition (2024-11-22) → Apache-2.0 (2024-11-28)
Architecture & Codebase — including AI provenance
strongfrontend/src/utils/api.ts is 1,928 lines, 20× this codebase's median file
adequateThe median source file here is 92 lines. 7 files exceed 1,000 lines, the largest being 1,928. 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.
frontend/src/utils/api.ts:1 — 1,928 lines (20× median) |
frontend/src/components/Dashboard.tsx:1 — 1,811 lines (19× median) |
backend/pyspur/api/slack_management.py:1 — 1,530 lines (16× median) |
frontend/src/components/nodes/nodeSidebar/NodeSidebar.tsx:1 — 1,529 lines (16× median) |
backend/pyspur/api/workflow_run.py:1 — 1,359 lines (14× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate7 test files against 338 source files (2.1%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 7 test files / 338 source files |
Product & Engineering Maturity
adequate0% of bug fixes add or change a test
adequateOf 581 fixes in the last 24 months, 0 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.
| 0 of 581 |
Security & Reliability Posture
adequateThe build runs third-party code it does not pin
adequate6 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/release.yml:28 — action pinned by tag |
.github/workflows/release.yml:31 — action pinned by tag |
2 outbound calls can wait forever
adequate2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
backend/pyspur/nodes/integrations/mathpix/pdf_to_latex.py:74 — outbound call without a timeout |
backend/pyspur/nodes/integrations/meta/ad_library.py:105 — outbound call without a timeout |
Relicensed: Apache-2.0 with additional terms → Apache-2.0 with a branding condition (2024-11-22) → Apache-2.0 (2024-11-28)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
1 advisory against this project in the last 24 months
adequateThe newest was published on 2025-06-23. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries.
| 2025-06-23: GHSA-8gff-cf92-72pv (low): pyspur Incomplete Filtering of Special Elements allowed by SingleLLMCallNode function |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 395 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 395 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No 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 395 files for 10 structured logging libraries; 0 matched |
One 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on pyspur-dev/pyspur: 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.