Read 2026-10-23
lunarphp/lunar: technical due diligence, read from its repository
What Borehole read in lunarphp/lunar's code and history at 82f6e4a: 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 | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongNo finding.
Engineering Process & SDLC Maturity
adequate5% of recent commits change more than 2,000 lines
adequate20 of 372 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.
| 20 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest pre-release, 2.0.0-alpha.6, is not on the branch this survey read; the newest release on it is 1.5.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 2.0.0-alpha.6 |
Security & Reliability Posture
strong7 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.
packages/admin/package.json:13 — ^4.0.0 |
packages/admin/package.json:14 — ^0.19.2 |
packages/admin/package.json:15 — ^4.1.5 |
packages/admin/package.json:16 — ^2.7.1 |
packages/admin/package.json:17 — ^0.1.13 |
The 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/document-facades.yml:27 — action pinned by tag |
.github/workflows/document-facades.yml:35 — action pinned by tag |
Observability & Operations
not assessableNot 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on lunarphp/lunar: 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.