open-source-parsers/json
stale
significant_divergence
Selected Prefer this fork only if you specifically need the 2015-era behavior or its bundled test/benchmark assets. For most users, current upstream is the better choice because this fork is stale and materially behind.
Corvusoft/json-dependency
stale
significant_divergence
Choose this fork only if you need its older vendor-specific behavior or packaging changes and are prepared to maintain it yourself. For most adopters, upstream nlohmann/json is the safer choice because it is active, current, and far better maintained.
ILCOINDevelopmentTeam/json
stale
significant_divergence
Prefer this fork only if you need an older, customized nlohmann/json snapshot and are prepared to own maintenance. If you want a current, broadly supported JSON dependency, upstream is the safer choice.
lefticus/json
stale
significant_divergence
Choose this fork only if you need its frozen older behavior or local compatibility patches. If you want an actively maintained JSON dependency, upstream is the better default.
philsquared/json
stale
significant_divergence
Prefer upstream unless you specifically need this fork’s legacy behavior or custom serializer work. This fork is too old and too divergent for general adoption, but it can be useful as a pinned historical baseline for maintenance or forensic work.
eclipse-score/nlohmann_json
active
significant_divergence
Prefer this fork if you need Eclipse Score's added workflow, documentation, and validation layers around nlohmann/json. Prefer upstream if you want the most current, low-friction JSON library with minimal divergence and upgrade risk.
FrancisBFTC/json
stale
significant_divergence
Choose this fork only if you need a customized downstream copy and can own the merge burden. If you mainly want the standard, well-maintained JSON library, upstream looks like the safer choice.
Madushankabro/json
stale
significant_divergence
Prefer this fork only if you specifically need its local fixes or a frozen 2021-era baseline. For most adopters, upstream is the safer choice because this fork is stale and materially behind.
commanderx16/json
stale
significant_divergence
Choose this fork only if you need its frozen, project-specific behavior and are prepared to own the maintenance burden. For general use, upstream is the better choice because it is active, far ahead, and much better maintained.
Prefer upstream unless you specifically need this exact frozen snapshot; the fork adds no visible capabilities and is materially behind current upstream maintenance.