Borehole · Project · free tier
perspective-dev/perspective
Free reading: not for reliance
8bf2cfb · 6,793 commits · 1,869 files
Read 2026-10-23

perspective-dev/perspective: technical due diligence, read from its repository

What Borehole read in perspective-dev/perspective's code and history at 8bf2cfb: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturityadequate
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • CONTRIBUTING.md:93: states a policy on AI-generated contributions
  • README.md:155: names OpenJS Foundation

Architecture & Codebase — including AI provenance

strong
01.6

rust/perspective-server/cpp/perspective/src/cpp/server.cpp is 4,170 lines, 33× this codebase's median file

adequate

The median source file here is 126 lines. 18 files exceed 1,260 lines, the largest being 4,170. 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.

Engineering Process & SDLC Maturity

adequate
02.15

96 tests are switched off

adequate

96 skip markers across 37 of 459 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.

02.16

Tests are retried until they pass

adequate

The suite is configured to retry failing tests (tools/test/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

Evidence
tools/test/playwright.config.ts:267 — test retry
02.24

11% of recent commits change more than 2,000 lines

adequate

49 of 438 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.

Evidence
49 commits over 2,000 lines

Product & Engineering Maturity

strong

No finding.

Security & Reliability Posture

adequate
05.21

6 shell commands built from strings

adequate

6 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

Evidence
rust/metadata/build.mjs:24 — command run through a shell
rust/perspective-js/build.mjs:110 — command run through a shell
rust/perspective-python/build.mjs:109 — command run through a shell
05.26

52 locked dependencies have published vulnerabilities, 28 high or critical in what ships

adequate

52 of 1,350 locked dependencies match 151 published advisories in OSV, 83 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

Evidence
pnpm-lock.yaml — basic-ftp 5.0.5: GHSA-5rq4-664w-9x2c (critical), fixed in 5.2.0
pnpm-lock.yaml — handlebars 4.7.8: GHSA-2w6w-674q-4c4q (critical), fixed in 4.7.9; a development dependency
pnpm-lock.yaml — tar 7.5.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; a development dependency

Observability & Operations

not assessable

Not rated: only 4 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on perspective-dev/perspective: 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.