Borehole · Project · free tier
files-community/files
Free reading: not for reliance
0e3c17c · 7,193 commits · 2,379 files
Read 2026-10-04

files-community/files: technical due diligence, read from its repository

What Borehole read in files-community/files's code and history at 0e3c17c: 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 Maturityadequate
Security & Reliability Posturestrong
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • LICENSE: Relicensed: GPL-3.0 → EULA (2018-06-14) → Apache-2.0 (2018-07-13) → LGPL-3.0 (2018-12-27) → GPL-3.0 (2021-01-01) → MIT (2022-02-27)

Architecture & Codebase — including AI provenance

strong
01.6

src/Files.App/ViewModels/ShellViewModel.cs is 3,579 lines, 63× this codebase's median file

adequate

The median source file here is 56 lines. 11 files exceed 1,000 lines, the largest being 3,579. 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.3

Tests cover a thin slice of the codebase

adequate

22 test files against 1,171 source files (1.9%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.

Evidence
22 test files / 1,171 source files

Product & Engineering Maturity

adequate
04.19

1% of bug fixes add or change a test

adequate

Of 329 fixes in the last 24 months, 2 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
2 of 329

Security & Reliability Posture

strong
05.27

The build runs third-party code it does not pin

adequate

7 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.

Evidence
.github/workflows/cd-sideload-preview.yml:46 — action pinned by tag
.github/workflows/cd-sideload-preview.yml:48 — action pinned by tag
05.60

Relicensed: GPL-3.0 → EULA (2018-06-14) → Apache-2.0 (2018-07-13) → LGPL-3.0 (2018-12-27) → GPL-3.0 (2021-01-01) → MIT (2022-02-27)

adequate

The root licence changed 5 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

Evidence
LICENSE — Apache-2.0 from 2018-07-13
LICENSE — LGPL-3.0 from 2018-12-27
LICENSE — GPL-3.0 from 2021-01-01
LICENSE — MIT from 2022-02-27

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 files-community/files: 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.