Read 2026-10-23
graphify-labs/graphify: technical due diligence, read from its repository
What Borehole read in graphify-labs/graphify's code and history at 92741d1: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:117: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
stronggraphify/extract.py is 11,274 lines, 79× this codebase's median file
adequateThe median source file here is 142 lines. 14 files exceed 1,420 lines, the largest being 11,274. 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.
graphify/extract.py:1 — 11,274 lines (79× median) |
graphify/extractors/engine.py:1 — 10,701 lines (75× median) |
graphify/cli.py:1 — 5,414 lines (38× median) |
graphify/extractors/resolution.py:1 — 4,309 lines (30× median) |
graphify/llm.py:1 — 3,856 lines (27× median) |
173 errors caught and discarded in product code
adequate173 places catch an error and do nothing with it, across 29 files (0.5 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
graphify/__main__.py:720 — error caught and discarded |
graphify/__main__.py:774 — error caught and discarded |
graphify/__main__.py:827 — error caught and discarded |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v1.0.0, is not on the branch this survey read; the newest release on it is v0.9.95. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.0.0 |
Security & Reliability Posture
adequate2 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.
| Slack token, where fakes are usual |
| JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate4 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/ci.yml:28 — action pinned by tag |
.github/workflows/ci.yml:94 — action pinned by tag |
12 locked dependencies have published vulnerabilities, 53 high or critical
adequate12 of 209 locked dependencies match 92 published advisories in OSV, 53 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. None of the high or critical ones is in what the product ships: they are development dependencies; they are optional extras of a package, installed only on request.
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,068 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 1,068 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 1,068 files for 10 structured logging libraries; 0 matched |
The service logs with print: 356 calls against 1 logger calls
adequate356 `print` or `console.log` calls in the service's code, and 1 calls through a logger. Printed lines carry no level and no context, cannot be switched off, and are hard to find again in production.
graphify/__main__.py:203 — print used for logging |
graphify/__main__.py:213 — print used for logging |
graphify/__main__.py:225 — print used for logging |
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 graphify-labs/graphify: 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.