Borehole · Project · free tier
filamentphp/filament
Free reading: not for reliance
154a22c · 30,083 commits · 8,383 files
Read 2026-10-04

filamentphp/filament: technical due diligence, read from its repository

What Borehole read in filamentphp/filament's code and history at 154a22c: 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 Maturityadequate
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed

Architecture & Codebase — including AI provenance

strong
01.3

Commit messages are templated rather than written

adequate

46% of commit subjects are exact repeats of another subject, and subject length varies by only 20.7 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
1771× 'wip'
962× 'chore: fix code style'
381× 'chore: styling'
01.6

docs-assets/screenshots/schema.js is 7,664 lines, 201× this codebase's median file

adequate

The median source file here is 38 lines. 17 files exceed 1,000 lines, the largest being 7,664. 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
docs-assets/screenshots/schema.js:1 — 7,664 lines (201× median)
packages/forms/resources/js/components/markdown-editor/EasyMDE.js:1 — 3,555 lines (93× median)
packages/tables/resources/views/index.blade.php:1 — 2,708 lines (71× median)
docs-assets/app/app/Livewire/TablesDemo.php:1 — 2,675 lines (70× median)
packages/support/resources/js/utilities/select.js:1 — 2,426 lines (63× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.19

18% of bug fixes add or change a test

adequate

Of 1416 fixes in the last 24 months, 252 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.

Evidence
252 of 1416
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, v5.8.4, is not on the branch this survey read; the newest release on it is v4.14.0. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag v5.8.4

Security & Reliability Posture

adequate
05.25

1 environment file is committed

adequate

docs-assets/app/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

Evidence
docs-assets/app/.env — committed environment file
05.22

6 deserialisers that can run code

adequate

6 places read data with a deserialiser that executes what it reads (PHP `unserialize`). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

Evidence
packages/actions/src/Exports/Jobs/ExportCsv.php:82 — code-executing deserialiser
packages/actions/src/Exports/Jobs/PrepareCsvExport.php:71 — code-executing deserialiser
packages/actions/src/Imports/Jobs/ImportCsv.php:80 — code-executing deserialiser
05.26

3 locked dependencies have published vulnerabilities, 1 high or critical in what ships

adequate

3 of 170 locked dependencies match 4 published advisories in OSV, 1 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.

Evidence
docs-assets/app/composer.lock — league/commonmark 2.10.0: GHSA-3q6v-r5mr-hxv8 (high), fixed in 2.10.2
docs-assets/app/composer.lock — laravel/framework 13.24.0: GHSA-jh5r-qr3c-85q8 (low), fixed in 13.30.0
docs-assets/app/composer.lock — league/flysystem 3.35.2: GHSA-cxf4-7mrp-vvpr (low), fixed in 3.35.3
05.65

14 advisories against this project in the last 24 months, 6 high or critical

adequate

The newest was published on 2026-09-23. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 4 records name filament with nothing tying them to this repository (CVE-2024-42485, CVE-2024-47817, CVE-2026-47740, …).

Evidence
2026-09-23: GHSA-7m6h-rg42-m449 (moderate), fixed in >= 5.8.3: Multi-factor authentication (app) management actions do not require password reauthentication
2026-08-17: GHSA-r3j6-gpjw-qfjr (moderate), fixed in >= 5.7.6: Multi-factor authentication (app) codes can still be used after a newer code has been used
2026-08-17: GHSA-xwpv-pqxp-5v36 (low), fixed in >= 5.7.5: Password validity disclosure for accounts denied panel access on login page
2026-08-17: GHSA-52xp-w8hr-xv3c (high), fixed in >= 5.7.0: Multi-factor authentication (app) can be bypassed when recovery codes are enabled
2026-06-17: GHSA-m9cv-24rx-8mv7 (high), fixed in >= 3.3.53: Disabled RichEditor field state can be used for XSS

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 filamentphp/filament: 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.