Discofork
Repository brief

chrislgarry/Apollo-11

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-30T13:04:49.338Z
3mo ago

chrislgarry/Apollo-11

A large, active mirror of the original Apollo 11 AGC source code for the Command Module (Comanche055) and Lunar Module (Luminary099). It is primarily a preservation/documentation repo, with many translations and ongoing transcription/proofing updates rather than application features.

GitHub
Loading tags...
Stars64,696
Forks7,388
Default branchmaster
Last pushed2026-01-22T06:10:28Z
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 this fork only if you specifically want its alternate source organization and are comfortable with a frozen, outdated snapshot. For most adopters, upstream is the better choice because it is much more active, better maintained, and richer in translations and transcription fixes.

Choose upstream unless you explicitly want an old frozen snapshot. This fork adds no visible capabilities and is far behind on maintenance and content updates.

Prefer upstream unless you need this exact old snapshot. This fork adds no visible capabilities, is 70 commits behind, and misses recent preservation and documentation work, so it is a poor choice for adopters who want the most accurate or current version of the Apollo 11 archive.

Prefer upstream unless you specifically want the fork's older, simplified browsing experience or its syntax-highlighting/compilation notes. For archival accuracy, completeness, and recent fixes, upstream is the better default.

Prefer upstream unless you specifically want a frozen, minimally changed copy. This fork adds nothing visible beyond the upstream repo and is behind on recent maintenance, so it is only attractive as an archival snapshot.

Prefer upstream unless you specifically want this fork’s frozen 2018-era state; the fork is substantially behind and stale, so it trades active correction and documentation progress for historical stability.

Prefer upstream unless you specifically want a frozen, unchanged snapshot from this fork point. This fork adds no visible functionality and is materially behind on documentation and source-text cleanup.

Prefer this fork only if the scan-viewing addition is the specific workflow you want and you are comfortable giving up upstream's later proofreading and translation work. For most adopters who care about transcription accuracy, upstream is the better default.

Prefer upstream unless you explicitly want an old, unchanged fork snapshot. This fork offers no added capabilities and is materially behind on preservation-focused updates, so adopters should expect missing transcription, documentation, and maintenance work.

Prefer upstream unless you specifically need this older frozen snapshot. The fork adds no visible capabilities and is far behind on maintenance, proofing, and translation work.