Apollo-11: The Original AGC Source Code as a Historical Artifact, Not a Modern Codebase
GitHub describes it as Original Apollo 11 Guidance Computer (AGC) source code for the command and lunar modules.. The repository metadata lists Assembly as its primary language. The metadata lists the NOASSERTION license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- This repository holds the transcribed assembly source for the Apollo 11 Guidance Computer, both command and lunar module versions. It is a primary historical document, not a buildable project, and its value is archival and educational.
- Who is it for?
- Adopt this repository if you are a historian, a retrocomputing enthusiast, or an educator who needs the exact transcribed source of the Apollo 11 AGC programs, Comanche055 and Luminary099. Do not adopt it as a codebase to build or extend; it has no releases and no conventional license.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 17 days ago.
- What is it written in?
- Mainly Assembly, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- chrislgarry/Apollo-1176,683 ★ · +4,624
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| chrislgarry/Apollo-11 | 72.1k | 76.7k |
4,624 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A Repository That Solves an Archival Problem, Not a Software Problem
The repository's source lives in two directories: Comanche055 and Luminary099. Comanche055 is part of Colossus 2A, the Command Module's AGC program. Luminary099 is part of Luminary 1A, the Lunar Module's program. Each directory holds the assembly source files, with headers that include the assembly revision and date. For example, Comanche055 is marked as revision 055, assembled April 1, 1969, and Luminary099 is revision 001, assembled July 14, 1969. This is not a codebase that evolves; it is a snapshot of a specific moment in the Apollo program.
What the Code Actually Is: Assembly for the AGC
The data flow is simple: you take the .agc files, feed them to yaYUL, and get a binary that can be loaded into an AGC emulator. The README points to Virtual AGC for anyone interested in compiling the original source. There is no build system and no tests; the only tooling is a markdown lint script defined in package.json. The code is meant to be read, not executed in a modern sense. The documentation is sparse, but the file headers contain the program name, revision, and date, which is enough to identify the exact version.
Getting It Running: The Virtual AGC Path
One thing to note: the README mentions that PRs are welcome for issues between the transcriptions and the original scans. You are not adding features; you are correcting transcription errors. If you find a discrepancy, you would open a pull request against this repository, but the actual compilation and testing would happen in Virtual AGC. This separation makes sense: this repo is the source of truth, and Virtual AGC is the toolchain.
The License Problem: NOASSERTION and Public Domain Claims
The contract and approvals section at the bottom of the README reproduces the original NASA contract details, including contract NAS 9-4065 with MIT. That is historical context, not a license grant. The code was written by NASA contractors, but the repository is a transcription. The README says the digitization was performed by Paul Fjeld, and the scans come from the MIT Museum. The license status of the transcription is unclear. If you plan to use this code in a commercial product, which is unlikely given its age and purpose, you would need legal advice. For educational use, the risk is low, but it is not zero.
A Real Limitation: It Is Not a Complete Flight Software Package
Another limitation is that the code is frozen in time. There are no GitHub releases and the core content is from 1969, but the last push was on 2026-10-29 and the repository is not archived, so it can still change when someone submits a correction. This means it does not receive security updates, bug fixes, or feature additions. That is fine for historical study, but it makes it useless for any modern application. The AGC hardware is long gone, and the software is only meaningful in an emulator.
Alternatives: Virtual AGC and the Original Scans
Another alternative is to go directly to the MIT Museum or the ibiblio.org scans. The README links to the scans for Luminary 099 and Comanche 055. Those scans are the original hardcopy images. If you are doing scholarly work, you should consult the scans, not just the transcription. The transcription might have errors, and the scans are the only way to verify. The Apollo-11 repository is a bridge to the scans, but it is not a substitute. For a casual user, the repository is enough to get a sense of the code; for a serious historian, the scans are necessary.
Maintenance and Upgrade Cost: Low, Because There Is Nothing to Maintain
The license implications are the main ongoing cost. Since the license is NOASSERTION, you cannot assume you have the right to redistribute or modify the code without further investigation. The README says public domain, but that is not a formal license. If you are a teacher who wants to include this code in a course, you should probably be fine, but you should document the source and the uncertainty. For a company, the uncertainty is a deal-breaker. The repository is a historical artifact, and treating it as a software dependency would be a category error.
Editorial conclusion
Adopt this repository if you are a historian, a retrocomputing enthusiast, or an educator who needs the exact transcribed source of the Apollo 11 AGC programs, Comanche055 and Luminary099. Do not adopt it as a codebase to build or extend; it has no releases and no conventional license. Before relying on it, verify the transcription against the original scans linked in the README, and check the Virtual AGC project for the current assembler and emulator. The repository is a reference artifact, and its maintenance is limited to correcting transcription errors.
Frequently asked questions
apollo 11 software code
The Apollo-11 repository holds the original Apollo Guidance Computer source for the command module as Comanche055, part of Colossus 2A, and for the lunar module as Luminary099, part of Luminary 1A. Both were transcribed from digitized images of a hardcopy held at the MIT Museum.
Can I compile the Apollo-11 source code from this repository?
Not from this repository alone. The readme says that if you are interested in compiling the original source code you should check out Virtual AGC, and the repository itself ships no build script and no compiler. Its only dependency is markdownlint-cli2, used for a lint script.
What license is the Apollo-11 source code under?
The attribution table in the readme states Copyright as Public domain, and a LICENSE.md file sits at the root of the repository. The license metadata for the repository itself reads NOASSERTION, so automated license detection does not resolve it without reading the file.
What kind of changes does Apollo-11 accept?
Pull requests are welcome for issues identified between the transcriptions in the repository and the original source scans for Luminary 099 and Comanche 055, and for any files that may have been missed. The readme asks that you read CONTRIBUTING.md before opening a pull request.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/chrislgarry-apollo-11)Star history chart for your README
[](https://hysenlabs.com/projects/chrislgarry-apollo-11)Was this useful?