Read 2026-10-04
ranchero-software/netnewswire: technical due diligence, read from its repository
What Borehole read in ranchero-software/netnewswire's code and history at 626f08c: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:23: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongiOS/SceneCoordinator.swift is 2,690 lines, 36× this codebase's median file
adequateThe median source file here is 74 lines. 17 files exceed 1,000 lines, the largest being 2,690. 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.
iOS/SceneCoordinator.swift:1 — 2,690 lines (36× median) |
Mac/MainWindow/MainWindowController.swift:1 — 1,803 lines (24× median) |
Modules/Account/Sources/Account/Account.swift:1 — 1,591 lines (21× median) |
iOS/MainFeed/MainFeedCollectionViewController.swift:1 — 1,514 lines (20× median) |
iOS/MainTimeline/MainTimelineModernViewController.swift:1 — 1,460 lines (19× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate6% of bug fixes add or change a test
adequateOf 651 fixes in the last 24 months, 42 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.
| 42 of 651 |
Security & Reliability Posture
adequate9 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: Google API key, where fakes are usual |
The 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.
Mac/Resources/Info.plist:57 — cleartext allowed app-wide |
iOS/Resources/Info.plist:66 — 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 ranchero-software/netnewswire: 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.