# micro1 GitHub data: what code adds to a corpus

> micro1 GitHub data: GitHub is on micro1's manifest list. How big repos run next to other tools, what Spirit's code archive shows, and what to check.

By Matt Burns, Vaultfish. Canonical: https://vaultfish.com/answers/micro1-github-data  
Published: 2026-09-08  
Updated: 2026-10-14

## The short answer

In an undated recorded forum talk, micro1 said its data manifest form asks which services a company uses, and GitHub is on that list. micro1's pages name neither GitHub nor a code payment. GitHub recommends repositories under 1 GB, so code is usually a small line in a storage count.

Code sits in the [micro1 data partnership](/guides/micro1-data-partnership) manifest beside documents and chat. The size rule and the rights rule both work differently for it.

## What did micro1 say about GitHub?

Only that GitHub is one of the services the data manifest form asks about, with a rough size for each (self-reported, recording, date not stated). The talk gave no code-specific rule or price.

## How big is code next to your other records?

In the same undated talk, [micro1](/buyers/micro1) staff named about 1 TB across the corpus as an earlier figure. Its current pages state no data-size threshold.

GitHub recommends repositories under 1 GB and strongly recommends under 5 GB, and blocks files over 100 MiB ([GitHub Docs](https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github)).

At 5 GB a repository, 1 TB would take 200 of them. For most companies the manifest total will come from other tools, and GitHub is a smaller line.

## Why would a lab want code at all?

A repository holds more than the latest files. Commits, reviews and issues show how people worked, which is the trail labs describe. The Spirit archive carried around 30 million lines of code beside 100 million emails and 500 million Teams messages ([Time](https://time.com/article/2026/08/25/google-spirit-airlines-ai-data-RL/)). Our [Spirit page](/answers/micro1-spirit-airlines) covers the case.

## Do you own the code?

That depends on your employment and contractor agreements, your customers' contracts and the open source licenses in your dependencies.

I found no verified figure for a single repository, and micro1 published none. Our [source code page](/answers/can-i-sell-source-code-to-ai) lists the questions to take to counsel.

## What should you do first?

Ask whoever administers your GitHub organization for a repository count and a rough total size. Then run the [rights check](/rights-check) on code separately from documents. Talk to a privacy or commercial lawyer in your state before you sign.

micro1 may pay us a referral fee if a company we introduce goes ahead with it. [How we are paid](https://vaultfish.com/disclosure)

Figure: scale, GitHub's repository size guidance: Recommended under 1 GB, Strongly recommended under 5 GB (emphasized). GitHub sets a soft size limit for repositories and a firmer one above it. Source: GitHub Docs, About large files on GitHub.

[Apply to micro1's data partnership (paid link)](https://req.micro1.ai/post/74520e8b-4673-4da5-b855-53609aaf6710?referralCode=f82e519e-5d64-4e0e-9574-760c84371cf2&utm_source=referral&utm_medium=share&utm_campaign=data_referral) · [micro1's own data-partnerships page](https://www.micro1.ai/data-partnerships)

_Paid link. [How we are paid](https://vaultfish.com/disclosure)_

_Vaultfish helps you run the process. We are not lawyers and this is not legal advice. If you need counsel who knows this area, we can point you to one._

## Sources

- [GitHub Docs](https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github)
- [Time](https://time.com/article/2026/08/25/google-spirit-airlines-ai-data-RL/)
- [micro1 data partnerships](https://www.micro1.ai/data-partnerships)
- [micro1 company referral](https://www.micro1.ai/company-referral)
- [micro1 referral terms](https://www.micro1.ai/legal/referral-terms)