Discofork
Repository brief

dkhamsing/open-source-ios-apps

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T11:58:00.117Z
3mo ago

dkhamsing/open-source-ios-apps

A large, actively maintained curated index of open-source iOS-family apps, not a standalone app. The repo is a collaborative catalog for iOS, iPadOS, watchOS, tvOS, and visionOS projects, with 1,647 listed projects, 49,427 stars, and 5,747 forks. It is updated frequently and the README is generated from `contents.json`.

GitHub
Loading tags...
Stars49,427
Forks5,747
Default branchmaster
Last pushed2026-03-29T13:35:01Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer upstream unless you need this fork’s older snapshot or its custom generation workflow. For active catalog use, upstream is clearly better; for historical or experimental maintenance, this fork may still be useful.

Choose upstream unless you specifically need this fork's older snapshot or custom generation tooling. For most adopters, the fork is too stale and too far behind to be a better default than the active upstream.

Prefer upstream unless you specifically want a frozen 2017-era snapshot or plan to build on the fork's custom automation. For anything that depends on current app discovery or maintained metadata, this fork is too stale.

Choose this fork only if you want a frozen, lightly customized version of the catalog. If you want current discovery coverage and active maintenance, upstream is clearly the better choice.

Choose this fork only if you specifically want a Titanium-only catalog and are comfortable with an old, heavily diverged snapshot. For general iOS-family discovery, upstream is clearly preferable.

Prefer this fork only if you need a historical or simplified version of the catalog. For active discovery, contribution, or current app listings, upstream is the better choice.

Prefer upstream unless you specifically need the older fork state; this fork is too stale for normal discovery or contribution workflows.

Prefer upstream for an up-to-date curated catalog. Choose this fork only if you specifically want an older, customized snapshot of the repository or intend to build on its local workflow changes.

Prefer upstream unless you explicitly want an old frozen copy or a fork to remix. This fork is not a better live catalog; it is mainly a historical, heavily outdated variant with some custom generation infrastructure.

Prefer upstream if you want the current, authoritative directory. Prefer this fork only if you specifically want the Netlify-hosted mirror or its custom publishing workflow and can tolerate outdated catalog data.