uscilab/cereal

A C++11 library for serialization

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 14th, 2026
Created on June 25th, 2013
Open Issues & Pull Requests: 345 (+0)
GitHub issues: Enabled
Number of forks: 843
Total Stargazers: 4,707 (+0)
Total Subscribers: 147 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.7 days
Mean response time: 254.7 days
90th percentile: 707.0 days
Tracked items: 34

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 37
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 888 days
Stale 30+ days: 36
Stale 90+ days: 35

Recent activity

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

Top labels

  • inactive (1)
  • tech support (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

cereal is a C++11 library for serialization that enables developers to convert C++ objects to and from various formats for storage or transmission.

The library addresses the problem of converting complex C++ data structures into serialized form and reconstructing them later. It works by providing built-in support for standard library types and allowing developers to write custom serialization functions for their own types. Users then employ serialization archives to handle the actual loading and saving of data. The approach emphasizes ease of use through straightforward APIs and comprehensive documentation.

Developers should choose cereal for projects requiring object serialization in C++11 and later. It suits applications that need to persist data structures or communicate them across systems. The library provides built-in support for standard library containers and types, reducing boilerplate code for common use cases. Custom types can be serialized by writing dedicated serialization functions, giving developers control over how their data is handled.

The project maintains active build verification across multiple platforms including Linux, macOS, and Windows through continuous integration. The maintainers sustain a mailing list for community discussion and support. Documentation is treated as a primary concern, with the README emphasizing that cereal has comprehensive documentation available on its dedicated web page.