r-lyeh/single_file_libs

List of single-file C/C++ libraries, with emphasis on clause-less licenses.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 51 minutes ago
Added to GitGenius on September 6th, 2026
Created on October 7th, 2016
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 650
Total Stargazers: 9,996 (+0)
Total Subscribers: 318 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1044.2 days
Mean response time: 1110.0 days
90th percentile: 2480.3 days
Tracked items: 97

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 429 days
Stale 30+ days: 6
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • pending (3)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

single_file_libs is a curated list of single-file C and C++ libraries emphasizing minimal dependencies and permissive licensing.

The project addresses the friction of integrating external code into projects by cataloging libraries designed for easy inclusion. Rather than requiring complex build systems or dependency management, these libraries are structured to be dropped directly into a codebase with minimal setup. The emphasis on single-file or two-file designs and clause-less licenses means developers can integrate functionality without navigating complex licensing terms or managing multiple source files.

Developers should choose this list when building projects that prioritize simplicity and portability over feature richness. It suits embedded systems, game development, and applications where keeping the dependency tree shallow matters. The collection requires that libraries compile on both 32-bit and 64-bit platforms and work across multiple operating systems, making it valuable for cross-platform work. The project does not position itself against other package managers or dependency systems; instead, it serves a different use case where self-contained libraries are preferable.

The project maintains an open submission process through pull requests, issues, and a Discord channel, indicating active community contribution. The maintainers have established clear inclusion rules around licensing, platform support, and file count limits, suggesting a structured approach to curation. The repository does not claim to have personally verified the quality or correctness of listed libraries, placing responsibility on users to evaluate entries before adoption.