buger/jsonparser

THE fastest alternative JSON parser for Go that does not require schema

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 12th, 2026
Created on March 20th, 2016
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 459
Total Stargazers: 5,653 (+0)
Total Subscribers: 97 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 206.7 days
Mean response time: 636.3 days
90th percentile: 1926.3 days
Tracked items: 63

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 3% of issues opened in the past year have been closed. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 38 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (2)
  • breaking (1)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

jsonparser is a JSON parser for Go that does not require schema definition.

The tool solves the problem of parsing JSON from unpredictable third-party APIs without needing to define structs or use slow generic maps. It works by allowing direct field access through path-based lookup on raw JSON bytes, avoiding the overhead of unmarshaling into intermediate data structures. The parser achieves significant performance gains—up to 6.5 times faster than the standard library's encoding/json package—while allocating no memory during parsing operations.

Developers should choose this tool when working with dynamic or complex JSON payloads where schema definition is impractical or when performance is critical. It suits projects that consume multiple third-party APIs with varying structures, or applications processing large volumes of JSON where memory allocation becomes a bottleneck. The tool offers optional lenient parsing modes for non-standard JSON inputs like single-quoted strings, while maintaining strict RFC 8259 compliance by default. It also provides streaming support through ReaderParser for processing large documents without loading them entirely into memory.

The project has undergone formal verification to L3 assurance level, with every public API traced to formal requirements and tested to 100% Modified Condition/Decision Coverage. The verification process discovered and fixed seven bugs that had escaped years of community use and standard fuzzing, including panic conditions from unchecked dereferences, a silent data-loss bug in the Set operation, and a malformed-output bug in Delete. The tool uses a structure-aware JSON fuzzer capable of generating grammar-valid mutations at high speed, and has executed over 16 million fuzz test cases combining structure-aware, path-mutation, and differential testing approaches.