Borehole · Project · free tier
laravel/cashier-stripe
Free reading: not for reliance
676765c · 2,128 commits · 134 files
Read 2026-10-23

laravel/cashier-stripe: technical due diligence, read from its repository

What Borehole read in laravel/cashier-stripe's code and history at 676765c: 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 Maturitystrong
Product & Engineering Maturitynot assessable
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.3

Commit messages are templated rather than written

adequate

36% of commit subjects are exact repeats of another subject, and subject length varies by only 20.3 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.

Evidence
100× 'Update CHANGELOG.md'
95× 'version'
89× 'Update CHANGELOG'
01.6

src/Subscription.php is 1,655 lines, 19× this codebase's median file

adequate

The median source file here is 83 lines. 2 files exceed 1,000 lines, the largest being 1,655. 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.

Evidence
src/Subscription.php:1 — 1,655 lines (19× median)
src/Invoice.php:1 — 1,095 lines (13× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

not assessable
04.1

Change keeps returning to the same few files

adequate

Five files out of 240 absorb 28% 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.

Evidence
src/Cashier.php — 231 commits touched it
src/Subscription.php — 162 commits touched it
composer.json — 137 commits touched it
src/Billable.php — 129 commits touched it
src/SubscriptionBuilder.php — 94 commits touched it

Security & Reliability Posture

strong

No finding.

Observability & Operations

not assessable

Not 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 assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on laravel/cashier-stripe: 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.