Read 2026-10-04
wordpress-mobile/wordpress-ios: technical due diligence, read from its repository
What Borehole read in wordpress-mobile/wordpress-ios's code and history at 4ce650b: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| 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
strongWordPress/Classes/ViewRelated/Aztec/ViewControllers/AztecPostViewController.swift is 3,742 lines, 50× this codebase's median file
adequateThe median source file here is 74 lines. 22 files exceed 1,000 lines, the largest being 3,742. 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.
WordPress/Classes/ViewRelated/Aztec/ViewControllers/AztecPostViewController.swift:1 — 3,742 lines (50× median) |
WordPress/Classes/ViewRelated/Notifications/Controllers/NotificationsViewController/NotificationsViewController.swift:1 — 2,260 lines (30× median) |
WordPress/Classes/Utility/Analytics/WPAnalyticsEvent.swift:1 — 2,134 lines (28× median) |
WordPress/Classes/ViewRelated/Reader/Controllers/ReaderStreamViewController.swift:1 — 1,898 lines (25× median) |
WordPress/Classes/ViewRelated/Blog/Blog Details/BlogDetailsTableViewModel.swift:1 — 1,693 lines (22× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 27.3, is not on the branch this survey read; the newest release on it is 25.0. The shipped product may differ from what this report describes. Survey the release branch too. This was read from the most recent 50,000 commits (21 Feb 2018 to 25 Sep 2026) only; older history was not read.
| tag 27.3 |
Security & Reliability Posture
adequateThe app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
Sources/Jetpack/Info.plist:583 — cleartext allowed app-wide |
Sources/WordPress/Info.plist:508 — cleartext allowed app-wide |
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 wordpress-mobile/wordpress-ios: 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.