Read 2026-10-23
vectifyai/pageindex: technical due diligence, read from its repository
What Borehole read in vectifyai/pageindex's code and history at e4669cf: 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 | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate41% of commit subjects are exact repeats of another subject, and subject length varies by only 25.9 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 118× 'Update README.md' |
| 22× 'fix notebook' |
| 10× 'fix' |
pageindex/client.py is 2,892 lines, 13× this codebase's median file
adequateThe median source file here is 222 lines. 1 file exceed 2,220 lines, the largest being 2,892. 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.
pageindex/client.py:1 — 2,892 lines (13× median) |
Engineering Process & SDLC Maturity
strongAlmost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 180 tracked files |
Product & Engineering Maturity
strongChange keeps returning to the same few files
adequateFive files out of 279 absorb 33% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
README.md — 209 commits touched it |
pageindex/client.py — 63 commits touched it |
pageindex/utils.py — 46 commits touched it |
pageindex/page_index.py — 41 commits touched it |
tests/test_client.py — 40 commits touched it |
Security & Reliability Posture
strong10 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.
requirements.txt:1 — >=1.105.1,<1.106 |
requirements.txt:2 — >=1.70.0 |
requirements.txt:3 — >=2.28.0 |
requirements.txt:5 — >=1.26 |
requirements.txt:6 — >=0.20.0 |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-05-11. 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 0.4.6. Answer lives in: the release you run, set against each fixed version.
| 2026-05-11: CVE-2026-8318 (moderate): A security flaw has been discovered in VectifyAI PageIndex up to f50e52975313c6716c02b20a119577a1929decba. Affected by this vulnerability is the function toc_tr |
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 vectifyai/pageindex: 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.