single_file_libs: a table of C and C++ leads nobody has verified
List of single-file C/C++ libraries, with emphasis on clause-less licenses.
At a glance
- What is it?
- single_file_libs is a Markdown table, in a repository whose only tracked top-level entries are README.md and .github/, that collects small C and C++ libraries and steers readers toward public-domain licensing. Its own front page states that no listed library has been verified, which makes it a directory of leads rather than a set of vetted dependencies.
- Who is it for?
- Use this list as a filter, not as a dependency. It narrows the field to libraries that are meant to be small, portable across 32-bit and 64-bit targets, and (for the highlighted ones) licensed without clauses, but it cannot tell you which of those is correct, current, or safe to ship.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 89 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
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
- r-lyeh/single_file_libs10,036 ★ · +26
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| r-lyeh/single_file_libs | 10k | 10k |
26 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The repository ships a README and a .github directory, and no code at all
Everything this project publishes lives in one Markdown file. The only tracked top-level entries are README.md and .github/, so there is no source tree, no build script, and no package manifest at the root, and the default branch is master. The repository has no GitHub releases, which means there is no tag, no archive, and no artifact a package manager could resolve. Getting the list is therefore a read operation rather than an install: open README.md on master, or copy the file into whatever notes you keep. Consuming it is also a read operation, because the data is a Markdown grid with no companion export, so any tool that wants it programmatically has to parse prose formatting. The practical consequence is that there is nothing to pin. When a row is corrected or a library is dropped, your fork and your local copy will not tell you, and the only way to keep notes reproducible is to record the commit you read instead of pointing at master.
One table packs file count, language, and license into a single parenthetical
The main listing is a Markdown table where each row carries four things: an informal tag, a hyperlink to the library, a parenthetical with file count, language, and license, and a short description. The opening rows look like this:
"misc" |[TinyRISCV64](https://github.com/neilstephens/TinyRISCV64.git) (1 C++, MIT) |RISC-V RV64IM Virtual Machine
*2d* |[Blendish](https://hg.sr.ht/~duangle/oui-blendish) (1 C, MIT) |Blender-style widget rendering using NanoVG
*2d* |[Cgl](https://github.com/Jaysmito101/cgl) (2 C, MIT) |C Game Library
*2d* |[Cimg](https://cimg.eu/) (1 C++, CeCILL) |Image processing toolkit (60K LoC)In the TinyRISCV64 row the leading digit is the file count, so Cgl is a two-file C entry and Immediate2D is a two-file C++ entry whose PD marks public domain. GlyType is written with a stray comma between the count and the language, which tells you the field is maintained by hand rather than generated, and the spacing inside the parentheses is inconsistent row to row. Cimg is listed at 60K LoC, a scale well away from the small-library premise the page opens with. The tag column is looser still: one tag is written in quotes and another in italics, so treat tags as editorial scribbles. There is no controlled vocabulary to filter on, and no way to tell whether a missing category means the list has no entries for it or has simply never been written down.
The front page tells you not to trust the entries, and the burden lands on you
The most consequential line on the page is a disclaimer, and it is worth reading before anything else: 'However, we have not personally verified that any specific library is as advertised, or is quality software.' That one sentence moves the entire burden of checking onto the reader, and it applies to every column in the table. The file count, the language, and the license name are unverified, so a project that grows past two files or changes license keeps its row unchanged until somebody notices. Corrections are accepted through a Pull Request, a new Issue, or a message in the discord channel, which means accuracy depends entirely on outsiders caring enough to file. So a row is a lead with an address attached, nothing more. The consequence for your codebase is concrete: budget your own time for the one field that carries legal weight, the license, and verify it by opening the header and source of the library you intend to vendor, since those files are exactly where the rules require the terms to appear.
Two files is the ceiling, and the escape hatch from it is undefined
Five conditions decide whether a library earns a row. It must be usable from C or C++, ideally both. It must include the licensing terms in the header and source files. It should be usable from more than one platform, ideally all major desktops and/or all major mobile. It should compile and work on both 32-bit and 64-bit platforms. And it should use at most two files, one header and one source, where the page goes further and says more than two files are mostly forbidden. Each condition is a claim about a library's shape rather than its quality, and the last one is qualified on the spot by a sentence saying exceptions will be allowed for good reasons. That escape hatch is not defined in the rules, which only say exceptions will be allowed for good reasons. The file-count column is the only practical filter you get, and the license-in-source requirement is the only rule you can check cheaply, because you can read it in the file you were going to copy anyway.
Corrections travel through a pull request, an issue, or a Discord invite
Three routes lead back to the maintainer: open a Pull Request, open a new Issue, or drop a message in the discord channel at https://discord.gg/2fZVEym. That same invite also sits as a banner link at the top of the page, and the server is described as a pleasant space to chat about C, C++, libs authoring, and game development specifically. There is a fragility in that contact surface worth naming: a Discord invite is a third-party redirect that can be revoked or expire, though the Pull Request and Issue routes the README also lists would still work.
Three sibling lists, then a long tail that is partly author profile pages
Three other lists are named as deliberately different from this one: STB, described as the mighty collection of gamedev utils; clib, a list of mostly small single C functions with licenses not listed; and CCAN, a package of lots of shareable C functions with mixed licenses. What follows is a long block headed And some more, and it mixes several kinds of pointer under one heading. Some entries are single libraries, such as klib, sokol, zpl, dr_libs, cute_headers, gb, par, and tm. Others are one author's whole output, and those arrive as filtered repository searches rather than projects: the links for andrewwillmott, blastbay, kokke, and rxi carry query strings that sort by language and type, so clicking one lands on a paginated list of everything that person has written rather than on a library you can read about. The consequence is that a single page carries three different levels of specificity at once, a curated table, three curated collections, and a directory of authors, and the page gives you no marker telling you which kind of pointer each line is.
No releases exist, and the last push is dated 2026-08-18
The maintenance picture is short and unambiguous. The repository is not archived, the default branch is master, and the last push is dated 2026-08-18. There are no GitHub releases, so no version identifier exists, and the activity signal is a commit that touches a Markdown file rather than a line of code. That is the right shape for what this is, a curated index that people read, and a push that recent says the list is still being worked on rather than abandoned. It is the wrong shape if you want a supply-chain signal. There is no changelog to read, so you cannot tell whether last month's edit added fifty rows or quietly removed the one you had planned to adopt. So snapshot the list, write down when you took it, and treat the diff between two commits as the only reliable way to learn that a row moved.
What the table cannot tell you before you commit to a library
Here is the honest inventory of the gaps. The list does not rank entries, and the only ordering on display is the tag column and the sequence of the table itself. It carries no benchmarks, no binary sizes, no compile-time or runtime measurements, and no indication of which platform each entry is actually known to build on. It says nothing about API stability, semantic versioning, or how often a library breaks between tags, and it links no build instructions, no test suite, no CI status, and no advisory database. Download counts, star counts, and per-library commit dates are out of scope as well. The license column is a name rather than a link to the license text, so it cannot tell you whether the terms are a short public-domain dedication or a full MIT or BSD text with clauses attached, which matters precisely because the project advertises an emphasis on clause-less licenses. The list therefore does one job well, narrowing the search to libraries that meet the stated rules, and hands you nothing about which of those to trust. That verification is your budget to spend, and the cheapest place to start is the license text inside the two files each entry promises to have.
Editorial conclusion
Use this list as a filter, not as a dependency. It narrows the field to libraries that are meant to be small, portable across 32-bit and 64-bit targets, and (for the highlighted ones) licensed without clauses, but it cannot tell you which of those is correct, current, or safe to ship. Before you vendor anything from a row, open the library's own header and source, read the license text there rather than the name in the table, confirm it is still one or two files, and record the commit of this list you read, because the last push was 2026-08-18 and the project publishes no release to compare against.
Frequently asked questions
What is a single header library?
In this list, it means a library usable from C or C++, ideally both, that ships as at most two files, one header and one source. The rules say more than two files are mostly forbidden, and the page states a preference for libraries that are C, public domain and single-file.
Are STL and STD the same?
The rules here say nothing about STL or STD, and this list is about small single-file libraries. Its stated requirements are that a library be usable from C or C++, include its licensing terms in the header and source files, work on more than one platform, and compile on both 32-bit and 64-bit platforms.
Is there a C++ library that contains everything?
This list does not present an all-in-one C++ library, since it collects small libraries rather than umbrellas. The closest neighbour it names is STB, described as the mighty collection of gamedev utils, which is filed under other related, but different lists rather than in the main table.
What are STB libraries?
The page names STB as the mighty collection of gamedev utils and points to the nothings/stb repository, filing it under other related, but different lists. So STB is a neighbour of this list rather than one of its rows.
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/r-lyeh-single-file-libs)Star history chart for your README
[](https://hysenlabs.com/projects/r-lyeh-single-file-libs)Was this useful?