Trending Tags Repositories Insights Dependencies Withheld

/

Trending Tags Repositories Insights Dependencies Withheld

Trending repositories

Ranked by Attention Score: stars gained over the last 180 complete days

Period

Sort order

Topics: json-serialization

Topics

Search topics

No listed topic matches. Press Enter to filter by “”.

Tag

Filters

Apply

Filters

Primary language

License

Total stars

Last push

Created

Archived

Clear all filters

5 repositories by Attention Score · May 7, 2026 – Nov 2, 2026 (UTC)

Topic: json-serialization

1.nlohmann / json

JSON for Modern C++

json
json-pointer
json-patch
cbor
msgpack
header-only
+13 more

C++MIT51K total7.5K forks

+1,625 stars

from 49,204 · score 7.39

2.okuramasafumi / alba

Alba is a JSON serializer for Ruby, JRuby and TruffleRuby.

json-serializer
json-serialization
ruby
performance
json
presenter
+1 more

Ruby MIT1.2K total65 forks

+52 stars

from 1,163 · score 3.97

3.alibaba / fastjsonArchived

FASTJSON 2.0.x has been released, faster and more secure, recommend you upgrade.

fastjson
java
android
json
json-parser
json-serialization
+4 more

Java APACHE-2.026K total6.4K forks

+40 stars

from 25,522 · score 3.71

4.danielaparker / jsoncons

A C++, header-only library for constructing JSON and JSON-like data formats, with JSON Pointer, JSON Patch, JSON Schema, JSONPath, JMESPath, CSV, MessagePack, CBOR, BSON, UBJSON, toon-format

json
cbor
jsonpath
csv
json-pointer
json-patch
+14 more

C++Other license855 total217 forks

+24 stars

from 831 · score 3.22

5.microsurging / surging

Surging is a micro-service engine that provides a lightweight, high-performance, modular RPC request pipeline. support Event-based Asynchronous Pattern and reactive programming.

microservices
apigateway
surging
rabbitmq
messagepack
protobuffer
+14 more

C#MIT3.3K total912 forks

+11 stars

from 3,252 · score 2.48

Order: Attention Score

Most net stars gained in the window first. The score only puts this gain on a log scale, so the order is the order of the gain.

How the ranking works

Ranked by stars gained in the window. The score is the natural log of one plus that gain, so a repository's rank is exactly its star gain's rank.

score = log1p(net stars gained in the trailing T complete UTC days)

A repository is ranked only when its Star History covers every day of the window and its latest Observation is not missing.

The longest window is 180 days. Star History from the Repository Host goes back at most 180 days before a repository's first Observation. A longer window needs more days of Observations first. A repository younger than the window is not ranked in it.

The filters narrow the same eligible repositories. A repository matches the topics when it has any of them. Total stars is the count now. Last push and creation on the Repository Host count back from the start of today (UTC). The counts beside the languages, licenses, and topics include all ranked repositories in the window. A Tag holds the repositories that have it; see Tags.

Repositories enter the index from the Seed Dataset or by gaining stars faster than the published admission threshold, whatever their size. Admission is permanent, so an archived repository can still rank.

Browse the Repository Index

Trending Tags Repositories Insights Dependencies Withheld Withholding Rule Health facts Privacy Send feedback

Powered by Workhorse · From the makers of AwesomeRepos