ohler55/oj

Optimized JSON

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 21st, 2026
Created on February 17th, 2012
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 268
Total Stargazers: 3,224 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.8 hours
Mean response time: 2.9 days
90th percentile: 3.6 days
Tracked items: 46

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: 209 days
Stale 30+ days: 6
Stale 90+ days: 2

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

Sign in to see which issues are moving.
Sign in

Detailed Description

Oj is a fast JSON parser and object marshaller for Ruby, implemented in C.

The tool addresses the performance bottleneck of JSON parsing and serialization in Ruby applications. It provides a C-based implementation that significantly outpaces the standard Ruby JSON gem. The parser offers multiple modes to handle different use cases: strict JSON compliance, compatibility with the standard JSON gem behavior, and compatibility with Rails and ActiveSupport conventions. This flexibility allows developers to drop in Oj as a replacement for existing JSON handling without rewriting application code.

Oj suits projects where JSON performance matters, particularly Rails applications handling high volumes of JSON serialization and deserialization. It works as a direct replacement for the standard JSON gem through its compatibility modes, making adoption straightforward for existing codebases. The tool includes an optimized parser accessible via Oj::Parser alongside traditional dump and load methods. Developers should consult the documentation for mode selection and configuration options, as the choice of mode affects behavior and performance characteristics.

The project maintains active development with regular releases and security support available through commercial subscription. Code contributions follow a structured process using the develop branch, and the codebase adheres to consistent formatting standards enforced through automated tooling.