Probably not. There is no hard minimum size for licensing code to AI labs, and small repos qualify when the code is real and yours. Value scales with the number of tokens in the code and in its git history, so a small repo earns less per license than a large one. A long, honest commit history lifts a small repo more than anything else.
Who the buyer is decides the answer. Acquisition marketplaces want revenue and users, so a small project with neither looks worthless there. AI labs license real source code and git history to train coding models, and they ignore revenue, users and polish. The license is non-exclusive, so you keep ownership and the same repo can be licensed again. A small amount per license can recur.
How small is too small to sell code?
There is no line count below which code is refused. Value per license is source tokens at $100 per million plus history tokens at $40 per million. A token is a short word or a few characters of code, so a small app holds far fewer than a million source tokens.
History is where small repos catch up. Every commit adds a diff, a message and context about how the code changed. A modest codebase worked on for a few years can hold many times more history than source. Across the program, history makes up 79% of licensed tokens.
Repos fall into three rough bands per license:
- Light: about $400 to $700. Small code, short history.
- Typical: about $1,000 to $1,500. A real product or tool with a steady history.
- Deep: about $2,500 to $4,000. Years of commits, tests and production patterns.
These are illustrative, conservative ballparks. Your real per-repo estimate appears within minutes once you connect Git.
What is a small repo worth?
Size is one input. The shape of the history matters as much. This table shows where common small repos tend to land and what moves them up.
| Repo profile | Rough band | What lifts it |
|---|---|---|
| Weekend script or bot | Light at best, up to $400 to $700 | Later commits that fix real problems |
| Side project, a few months of evenings | Light, $400 to $700 | A steady, unsquashed commit history |
| Small product, maintained for a year or more | Typical, $1,000 to $1,500 | Tests, bug fixes, real production use |
| Long-lived product, several years of work | Deep, $2,500 to $4,000 | Tests, years of history, production patterns |
Two things lower the number for any repo. Squashing history into a few commits removes most of the history tokens, so leave it as it is. Code mostly produced by a generator or an assistant says little about how a developer builds software, so labs value it less.
You do not need to tidy anything first. The code does not need to build or run, and no README is required. Secrets and personal data are stripped from a review copy before any buyer sees it.
Can I sell several small repos together?
Yes, and for small projects that is usually the point. You connect GitHub, GitLab or Bitbucket read-only and pick every repo you want to include. Each repo is estimated and licensed on its own, so a few light repos add up. Five light repos come to about $2,000 to $3,500 if each is licensed once, and each can be licensed again.
Most developers have more small repos than they remember: an old bot, a browser extension, a half-built app, a library they wrote for a job that never shipped. They are often spread across two or three accounts. Gather them into one list, check each one is yours, and submit them together. The sell a side project page covers abandoned and unfinished work, and sell a GitHub repository covers repos that live on GitHub.
What is genuinely too small to sell?
Some code has too little of its own in it to license. Leave these out:
- A few files. A single script, a config folder or a gist has too few tokens and almost no history.
- Generated boilerplate. A framework scaffold you never built on is the generator’s work.
- Forks you did not change. If most of the code is someone else’s, there is little of yours to license.
- Copied tutorial or course code. It exists in thousands of copies already.
- Public code. Anything public now or in the past is declined whatever its size, including old releases on npm or PyPI.
- AI-written code. The labs want code written by people and check for it.
- Code you do not own. Client work usually belongs to the client unless your contract says otherwise, and some employment contracts claim side projects. Without the rights, size does not matter.
If a repo sits on the edge, include it. The estimate tells you what it is worth, and you can withdraw any codebase later.
How do I find out what my small repos are worth?
Request access through get a valuation. It is free to join and there is no commitment. Once you sign and connect Git read-only, a real per-repo estimate appears within minutes, including for the small repos.
For the working behind the bands and what drives the number up, read how much is my code worth. For why labs pay for small, real code at all, read sell code for AI training.
Find out what your small repos would earn.
Free to join. No public listing. A real estimate in minutes once Git is connected.