jimhigson/oboe.js

A streaming approach to JSON. Oboe.js speeds up web applications by providing parsed objects before the response completes.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 14th, 2026
Created on March 11th, 2013
Open Issues & Pull Requests: 119 (+0)
GitHub issues: Enabled
Number of forks: 208
Total Stargazers: 4,815 (+0)
Total Subscribers: 91 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 222.0 days
Mean response time: 1003.9 days
90th percentile: 2747.6 days
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • docs (1)

Most active issues this week

Detailed Description

Oboe.js is a streaming JSON parser library that enables web applications to process parsed objects before the complete response arrives.

The library addresses the problem of waiting for entire JSON responses to download and parse before using any data. It takes a streaming approach, parsing JSON incrementally as it arrives and making partial results available immediately. This combines the convenience of DOM-style object access with the performance characteristics of event-driven SAX parsing. The tool can handle JSON trees larger than available memory, instantiate object-oriented models from JSON during parsing, and transform data while it streams.

Oboe.js suits projects where response latency matters and where you can act on partial data before a request completes. It works as a micro-library with no dependencies and integrates with any other JavaScript libraries in your stack. The tool is particularly valuable for loading large datasets or when you need to begin processing before the full response arrives, even if the request never completes.

The project is archived and has not received code changes in several years. The original author acknowledges that while the streaming JSON parsing gap in the market remains unfilled, the project is no longer actively maintained and recommends that new projects seek alternative solutions.