akheron/jansson

C library for encoding, decoding and manipulating JSON data

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 35 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 20th, 2026
Created on April 23rd, 2009
Open Issues & Pull Requests: 135 (+0)
GitHub issues: Enabled
Number of forks: 853
Total Stargazers: 3,367 (+0)
Total Subscribers: 122 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 619 days
Stale 30+ days: 11
Stale 90+ days: 8

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Jansson is a C library for encoding, decoding, and manipulating JSON data.

The library addresses the need to work with JSON in C programs, where native JSON support does not exist. It provides functions to parse JSON text into in-memory representations, serialize those representations back to JSON text, and perform operations on the resulting data structures. The approach centers on a simple API that handles the common tasks of reading JSON from strings or files and writing JSON output, along with utilities for inspecting and modifying JSON objects and arrays.

Jansson suits projects that require JSON handling in C without external dependencies or complex frameworks. It is particularly valuable for systems programming, embedded applications, and scenarios where lightweight JSON support is preferable to heavier alternatives. The library's straightforward interface makes it accessible for developers who need basic JSON functionality without learning an elaborate API.

The project maintains a stable, focused codebase with infrequent but deliberate updates. Development activity shows long intervals between releases, indicating a mature tool where the core functionality is considered complete. When changes do occur, they tend to address specific issues or edge cases rather than introduce major new features. The project does not show signs of rapid iteration or frequent breaking changes, suggesting it prioritizes backward compatibility and reliability over rapid feature expansion.