awesome-cpp: A Curated Map of the C++ Ecosystem, Not a Package Manager
A curated list of awesome C++ (or C) frameworks, libraries, resources, and shiny things. Inspired by awesome-... stuff.
At a glance
- What is it?
- awesome-cpp is a hand-maintained list of C++ and C libraries, tools, and resources. It helps engineers discover options, but its value depends entirely on how current and complete the maintainer keeps it.
- Who is it for?
- Adopt awesome-cpp if you are exploring the C++ landscape and want a broad, categorized starting point. It is useful for discovering libraries you did not know existed, especially across niche areas like biology or serial ports.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 4 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
- fffaraz/awesome-cpp74,440 ★ · +1,623
| Repository | 2026-08-18 | 2026-11-15 |
|---|---|---|
| fffaraz/awesome-cpp | 72.8k | 74.4k |
1,623 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What awesome-cpp Solves: Discovery in a Fragmented Ecosystem
C++ has no single official package repository. Libraries live on GitHub, personal sites, and institutional pages. Finding a library for a specific task often means asking a forum or guessing search terms. awesome-cpp addresses this by collecting links into one document, organized by category. It is for engineers who want to know what exists before writing code. The list covers everything from standard libraries to game engines, from AI to serial port communication. It also includes software tools like compilers and IDEs, plus resources such as books and talks. This breadth is its main strength. You can scan the table of contents and jump to a category that matches your problem.
How the List Is Structured: Categories, Links, and Licenses
The README is a single markdown file with a table of contents. Each category has a heading and a bullet list of projects. Each entry typically has a name, a link, and a short description. Some entries include a license tag in brackets, like [MIT] or [Apache2]. A few, such as Boost and Dlib, have a :zap: marker next to the link. The categories are specific and numerous: Standard Libraries, Frameworks, Artificial Intelligence, Asynchronous Event Loop, Audio, Biology, BitTorrent, Chemistry, CLI, Compression, Concurrency, and so on. There are also sections for Software (compilers, debuggers, build systems) and Resources (books, talks, podcasts). This structure makes it easy to find a starting point, but it is a flat list. There is no ranking, no version information, and no indication of whether a project is actively maintained, except for occasional tags like [retired] on Apache STDCXX.
How to Get It Running: Clone and Browse
awesome-cpp is not a library or a tool. You do not install it. You access it by visiting the GitHub repository or the homepage at http://fffaraz.github.io/awesome-cpp/. To work with it locally, you can clone the repository. The command is git clone https://github.com/fffaraz/awesome-cpp.git. After cloning, you have a README.md file that is the entire list. You can open it in any text editor or render it in a markdown viewer. There is no build step, no configuration file, and no API. The only way to interact with the list is to read it or to contribute via pull requests. The README invites contributions with a note: if you see a project or link that is no longer maintained or is not a good fit, submit a pull request to improve the document. That is the entire workflow.
The Real Limitation: Maintenance and Completeness Are Unknown
The repository has no GitHub releases, and its last push was 2026-10-31. A list like this only has value if it is current. The README includes a retired project (Apache STDCXX), which suggests that entries are not always pruned. The categories are broad, but the list cannot be exhaustive. For example, the Frameworks section includes many well-known projects like Boost and Folly, but it also includes niche ones like CGraph and Coost. The selection is subjective. The maintainer decides what is 'awesome'. There is no objective criterion. As a result, you might miss a library that is perfect for your use case simply because it was never added. Conversely, you might find a library that looks promising but is abandoned. The list gives you no way to distinguish between the two.
Alternatives: Package Managers and Other Curated Lists
If you need concrete versions and dependency management, awesome-cpp is not the right tool. Package managers like vcpkg and Conan offer a more structured approach. They provide a registry of libraries, each with a version, a build recipe, and a way to integrate into your build system. For example, vcpkg lets you install a library with vcpkg install <library-name>. That is a different approach: instead of a static list, you get a dynamic, queryable database. Another alternative is other awesome lists. The README itself points to a section called 'Other Awesome Lists', which suggests that the maintainer acknowledges the existence of similar lists. The key difference is that package managers give you a concrete artifact to use, while awesome-cpp only gives you a link to investigate.
What the List Does Not Tell You: Quality, Compatibility, and License Nuance
The list provides a link and a one-line description. It does not tell you whether a library is header-only, what C++ standard it requires, or whether it has dependencies. It does not tell you about build systems supported, platform support, or performance characteristics. The license tag is a single identifier, but it does not explain the implications. For instance, JUCE has a complex license: Core-Module is ISC, the rest is GPL2/GPL3 or Proprietary. The list shows this in a bracket, but you have to click through to understand what it means for your project. The list also does not indicate whether a project is actively maintained. The only hint is the occasional [retired] tag. So, you cannot use the list to make a quick decision. You must visit each repository and read its README, check its issues, and assess its activity. That is a time cost, but it is unavoidable with a curated list of this nature.
Who Should Use It and How to Get the Most Out of It
awesome-cpp is most useful for a developer who is starting a new project and wants a broad survey of what is available. For example, if you need a JSON library, you can go to the JSON section and see several options. You then have to research each one. The list saves you the initial search step. It is also useful for learning about the ecosystem. The Resources section includes books, talks, and podcasts, which can help you improve your C++ skills. To get the most out of it, use it as a starting point, not a final answer. Cross-reference entries with package managers or other sources. Check the GitHub repository for the list itself to see recent activity. If you find a stale entry, follow the contributing guideline and submit a pull request. That is the only way the list improves. The list is a community resource, and its quality depends on community participation.
Editorial conclusion
Adopt awesome-cpp if you are exploring the C++ landscape and want a broad, categorized starting point. It is useful for discovering libraries you did not know existed, especially across niche areas like biology or serial ports. Do not rely on it as an authority on library quality or maintenance status. The list does not rank entries, and the README includes retired projects like Apache STDCXX. Before adopting any library found here, verify its license, recent activity, and compatibility with your target C++ standard. Also, check the list's GitHub issues and pull requests to see if the entry is stale. If you need a more structured, versioned approach, use a package manager like vcpkg or Conan, which provide concrete versions and dependency resolution. For a quick scan, awesome-cpp is a good index, but treat every entry as a lead, not a recommendation.
Frequently asked questions
Is awesome-cpp still being updated?
The repository's last push was 2026-09-27 and it has no GitHub releases. Its Contributing section asks readers to open a pull request when a listed project is no longer maintained, so upkeep is a pull request process rather than a published version stream.
What licence does awesome-cpp use, and what about the projects it lists?
The list itself is MIT licensed, which covers the document of links only. Each listed project carries its own tag, and they differ: abseil-cpp is tagged Apache2, EASTL BSD, GLib LGPL, and JUCE is tagged Core-Module: ISC, Rest: GPL2/GPL3/Proprietary.
Does awesome-cpp recommend or rank the libraries it lists?
No. Entries are organised by category and carry a description and a licence tag, with no scores. The Standard Libraries section lists the C++ Standard Library, the Standard Template Library, the C POSIX library, the ISO C++ Standards Committee and the GNU C Library side by side without preferring one.
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/fffaraz-awesome-cpp)Star history chart for your README
[](https://hysenlabs.com/projects/fffaraz-awesome-cpp)Was this useful?