Primary question: Do you want to read or compile the exact AGC assembly code that landed humans on the Moon?
RepoDaily adoption score
RepoDaily rates this as 90/100 (strong) for adoption: evidence, installation path, production risk, differentiation, license clarity, and AI/agent fit are scored from the article sources and adoption notes.
4 source(s) across 3 source category/categories, plus a RepoDaily-specific evidence module when available.
6 workflow step(s), 5 next-action step(s), and 3 command/install signal(s) were detected.
Trending momentum is +1,195 stars, with maintenance/release/issue signals counted when present.
Risk is marked low, with 4 security note(s) and 3 explicit skip condition(s).
3 opportunity lens item(s), 3 alternative(s), and 3 type-specific section(s) support differentiation.
License source or license wording is present.
2 AI/agent-related signal(s) were detected in the article text and metadata.
Project overview
The chrislgarry/Apollo-11 repository contains the original Apollo Guidance Computer (AGC) source code for both the Command Module (Comanche055) and the Lunar Module (Luminary099). These are not simulations or rewrites — they are digitized transcriptions of the actual assembly programs that NASA assembled in 1969. Comanche revision 055 was assembled on April 1, 1969 at 10:28, and Luminary revision 001 of program LMY99 was assembled on July 14, 1969 at 16:27 — just six days before the Saturn V launched from Kennedy Space Center.
The code was digitized manually from paper printouts held at the MIT Museum. Paul Fjeld performed the digitization, and Deborah Douglas of the MIT Museum arranged access. The Virtual AGC project at www.ibiblio.org/apollo, maintained by Ron Burkey, provided the yaYUL assembler tooling and broader context. Because the transcription was performed by hand from physical documents, the repository explicitly acknowledges that typos and discrepancies exist and welcomes pull requests to reconcile the transcribed code against original scans.
The programs are written in AGC assembly language and assembled with yaYUL. The Command Module program is also referred to as Colossus 2A, developed under NASA contract NAS 9-4065 through the Instrumentation Laboratory, as documented in report R-577 under DSR project 55-23870. The entire codebase is public domain, meaning there are zero licensing restrictions on reading, copying, teaching, or adapting the code for any purpose.
With 1,195 period stars and trending rank 8 on July 22, 2026, the repository continues to draw attention decades after the code was first written. The README has been translated into more than 35 languages — from Japanese and Korean to Arabic, Hindi, and Nepali — and the project maintains a structured contribution workflow where volunteers proofread assembly listings against scanned printouts accessible at https://28gpc.csb.app/.
Practically speaking, GitHub provides built-in syntax highlighting for AGC assembly, so anyone can read the code directly in a browser without installing anything. For local study, community-maintained extensions exist for VS Code, Sublime Text, Vim, Atom, Eclipse, Kate, jEdit, TextPad, CodeBlocks, and ProgrammersNotepad. For those who want to go further and actually compile the source into runnable binaries, the Virtual AGC project supplies the yaYUL assembler and a full hardware emulator.
Why it is trending now
- Gained 1,195 stars in the trending period, reflecting renewed public interest in historically significant software
- Public domain license means zero restrictions on educational, commercial, or artistic reuse
- Over 35 language translations of the README make the project globally accessible
- Community-driven proofreading against original MIT Museum scans adds an ongoing collaborative dimension
- GitHub's built-in AGC syntax highlighting lets anyone read 1969 assembly code without special tooling
Problem it solves
- Preserves historically significant code that was previously accessible only through physical archives at the MIT Museum
- Makes 1960s real-time embedded systems engineering concrete and readable for modern developers and students
- Provides a tangible reference for understanding how guidance software was written under severe memory and processing constraints
- Reconciles manual transcription errors through structured community pull requests checked against scanned originals
How it works
- Browse the Comanche055/ directory for Command Module AGC code — Colossus 2A, assembled April 1, 1969
- Browse the Luminary099/ directory for Lunar Module AGC code — Luminary 1A, assembled July 14, 1969
- Read the assembly listings with AGC syntax highlighting built directly into GitHub's web interface
- Install a local editor extension such as the VS Code agc-assembly extension (github.com/wopian/agc-assembly) or the Vim plugin (github.com/wsdjeg/vim-assembly) for offline study
- Download Virtual AGC from www.ibiblio.org/apollo to compile the source using the yaYUL assembler and run the binaries in a full AGC emulator
- Compare any line of transcribed code against original scanned printouts at https://28gpc.csb.app/ and open a pull request if you find a discrepancy
How to Engage With the AGC Source Code
The fastest way to explore the repository is through GitHub's web interface, which provides native syntax highlighting for AGC assembly files. Navigate to Comanche055/ for the Command Module program (Colossus 2A) or Luminary099/ for the Lunar Module program (Luminary 1A). Each directory contains complete assembly listings with original NASA comments preserved verbatim, including historical notes from Margaret Hamilton's team and other MIT Instrumentation Laboratory engineers.
For local study, install the agc-assembly extension for VS Code (github.com/wopian/agc-assembly), the Vim plugin (github.com/wsdjeg/vim-assembly), or the Sublime Text package (github.com/jimlawton/AGC-Assembly). The CONTRIBUTING.md specifies formatting rules: tab indentation, tab width of 8, and trimmed trailing whitespace. Extensions marked with a dagger in CONTRIBUTING.md — Atom, Sublime Text 3, and VS Code — also support automatic formatting.
To compile the source, download Virtual AGC from www.ibiblio.org/apollo. The project includes the yaYUL assembler referenced in the README attribution table alongside a hardware emulator capable of running the compiled binaries. The contact person listed is Ron Burkey (info@sandroid.org).
Maintenance and Contribution Model
- Maintenance is primarily proofreading: contributors compare transcribed code against original MIT Museum scans at https://28gpc.csb.app/
- CONTRIBUTING.md requires that comments match the scans exactly — even original typographic errors made by NASA developers in 1969 are preserved deliberately
- Pull requests are accepted for discrepancies between the repository transcription and scanned originals for both Luminary 099 and Comanche 055
- package.json has zero runtime dependencies; markdownlint-cli2 (^0.16.0) is only a devDependency for linting documentation across root .md files, translations/, Comanche055/, and Luminary099/
- No security patches are needed — the repository is a static historical text archive, not executable software
Repository Linting Commands
- npm run lint — executes markdownlint-cli2 against all .md files in root, translations/, Comanche055/, and Luminary099/ using .markdownlint.yml configuration
- npm run lint:fix — same linting pass with the --fix flag to auto-correct markdown formatting issues
- Full underlying command: markdownlint-cli2 *.md translations/*.md Comanche055/*.md Luminary099/*.md --config .markdownlint.yml
Who should pay attention?
Good fit if
- Educators teaching computer architecture, embedded systems, or aerospace software history courses
- Developers curious about how real-time guidance software was written for the AGC under extreme hardware constraints
- Retro-computing enthusiasts who want to compile and run the code in the Virtual AGC emulator
- Writers, artists, and researchers who need public-domain reference material related to the Apollo program
- Volunteers interested in digital preservation by proofreading assembly listings against original scans
Skip for now if
- Teams looking for production-ready software to integrate into modern systems
- Developers who need an actively maintained library, framework, or API
- Projects that require ongoing feature development, bug fixes, or community support channels
Risks and cautions
This is a static historical archive of AGC assembly source code. There are no runtime components, no executable binaries, and no third-party dependencies to audit. The only tooling in the repository is markdownlint-cli2, used solely for documentation formatting.
- No executable runtime — the repository contains assembly source text listings, not compiled binaries
- package.json declares zero runtime dependencies; markdownlint-cli2 is a devDependency only
- Copyright is public domain — no license compliance obligations whatsoever
- Compilation requires the external Virtual AGC project (yaYUL assembler), which is outside this repository's scope
- Public domain — no license restrictions, attribution requirements, or compliance overhead
- No runtime code executes from this repository; it is a text archive
- No third-party runtime dependencies; only markdownlint-cli2 (^0.16.0) for documentation linting
- No network calls, no APIs, no data collection, no build pipeline that executes untrusted code
Alternatives to compare
| Approach | When to use | Trade-off |
|---|---|---|
Virtual AGC | When you want the full AGC emulation environment — assembler, emulator, and documentation — rather than just the raw source listings | Free / open source |
Scanned AGC Printouts (28gpc.csb.app) | When you need to verify a specific transcription against the original paper printout scans for Comanche or Luminary | Free |
ibiblio Apollo Archive | When you want the broader Virtual AGC project website with downloads, documentation, and historical context maintained by Ron Burkey | Free |
What this trend reveals
Teaching Real-Time Systems History
The AGC source is a concrete case study for teaching how engineers solved guidance, navigation, and resource-constrained computing problems. Students can read the actual assembly listings that controlled the lunar descent — not a textbook abstraction.
Check whether your computer science or aerospace engineering curriculum covers embedded systems, real-time scheduling, or software history. Assign students to read a specific routine from Luminary099 and trace its logic.
Contributing to Digital Preservation
Volunteers can pick a file from Comanche055 or Luminary099, cross-reference it character by character against scanned originals at https://28gpc.csb.app/, and submit pull requests for any discrepancies they find. CONTRIBUTING.md provides the proofreading guidelines.
Open CONTRIBUTING.md, select a file from Comanche055 or Luminary099, open the corresponding scan at 28gpc.csb.app, and compare at least 50 lines for transcription accuracy.
Compiling and Running the Code
The source can be compiled with yaYUL and executed in the Virtual AGC emulator, enabling live demonstrations of Apollo-era computing at conferences, classrooms, or museum exhibits.
Download Virtual AGC from www.ibiblio.org/apollo, follow the build instructions, and attempt to assemble either Comanche055 or Luminary099 into a runnable binary.
RepoDaily verdict
The Apollo-11 repository is a meticulously digitized, public-domain archive of the original AGC assembly code that guided the first Moon landing. It requires no installation, has no security surface, and carries no licensing obligations. Its trending resurgence reflects enduring fascination with how engineers in 1969 wrote reliable guidance software under extreme constraints — and the repository makes that code readable to anyone with a web browser.