randygaul/cute_headers

Collection of cross-platform one-file C/C++ libraries with no dependencies, primarily used for games

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 13th, 2026
Created on June 5th, 2016
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 311
Total Stargazers: 5,068 (+0)
Total Subscribers: 108 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 days
Mean response time: 79.6 days
90th percentile: 429.0 days
Tracked items: 15

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 372 days
Stale 30+ days: 6
Stale 90+ days: 5

Recent activity

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

Top labels

  • help wanted (3)
  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Cute_headers is a collection of single-file C/C++ libraries that provide cross-platform functionality for game development without external dependencies.

The collection addresses the friction of integrating multiple specialized libraries into game projects by packaging each feature as a self-contained header file. Developers include a header normally for declarations, then add a single preprocessor symbol in one translation unit to define the implementation. This approach eliminates build system complexity and dependency management while keeping distribution trivial—sharing code means copying a single file rather than managing archives or complex directory structures.

The libraries suit game developers and anyone building performance-sensitive applications who want reliable, focused implementations without pulling in large frameworks. The collection includes 2D collision detection with manifold generation, a game-oriented networking layer with optional reliability over UDP, Tiled map loading, sprite batching for efficient 2D rendering, audio playback with mixing and crossfading, PNG loading and saving with atlas compilation, Aseprite file parsing, synchronization primitives including thread pools, and TLS connections for HTTPS. Each library is designed for practical use in games rather than as a comprehensive toolkit. The single-file approach distinguishes this from traditional libraries that require separate build steps or dependency management.

Development activity shows consistent maintenance across the library collection. The project maintains active community engagement through a dedicated Discord channel and social media presence for questions and feedback. Individual libraries receive periodic updates as indicated by version tracking across the collection, suggesting ongoing refinement and bug fixes rather than abandonment. The presence of example code and test folders for multiple headers demonstrates attention to usability and developer experience.