canonical-json alternatives and similar packages

Based on the "JSON" category.
Alternatively, view canonical-json alternatives based on common mentions on social networks and blogs.

waargonaut

9.1 0.0 canonical-json VS waargonaut

JSON decoding/encoding/manipulation library.
aeson-typescript

8.8 7.0 canonical-json VS aeson-typescript

Generate TypeScript definition files from your ADTs

InfluxDB - Power Real-Time Data Analytics at Scale

Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

Promo www.influxdata.com

jsonifier

8.7 4.9 canonical-json VS jsonifier

Fast and simple JSON encoding toolkit
aeson-schemas

8.1 7.0 canonical-json VS aeson-schemas

Easily consume JSON data on-demand with type-safety
safe-json

7.2 5.1 canonical-json VS safe-json

Automatic versioning of JSON formats for Haskell data types (with backwards compatibility)
aeson-yaml

6.7 3.5 canonical-json VS aeson-yaml

Encode any Aeson (JSON) value as YAML (in pure Haskell)
aeson-combinators

6.2 5.3 canonical-json VS aeson-combinators

Aeson combinators for dead simple JSON decoding
jsonpath

5.5 0.0 canonical-json VS jsonpath

Haskell implementation of JSONPath
one-line-aeson-text

4.4 0.0 canonical-json VS one-line-aeson-text

Pretty-printing short Aeson values as text
sajson

3.6 0.0 canonical-json VS sajson

Haskell wrapper for sajson
aeson-decode

2.8 1.2 canonical-json VS aeson-decode

Easy functions for converting from Aeson.Value

Do you think we are missing an alternative of canonical-json or a related project?

Add another 'JSON' Package

Popular Comparisons

README

An implementation of Canonical JSON.

The "canonical JSON" format is designed to provide repeatable hashes of JSON values. It is designed for applications that need to hash, sign or authenitcate JSON data structures., including embedded signatures.

Canonical JSON is parsable with any full JSON parser, and it allows white space for pretty-printed human readable presentation, but it can be put into a canonical form which then has a stable serialised representation and thus a stable hash.

The basic concept is that a file in the canonical JSON format can be read using parseCanonicalJSON. Note that this input file does not itself need to be in canonical form, it just needs to be in the canonical JSON format. Then the renderCanonicalJSON function is used to render into the canonical form. This is then the form that can be hashed or signed etc.

The prettyCanonicalJSON is for convenience to render in a human readable style, since the canoncal form eliminates unnecessary white space which makes the output hard to read. This style is again suitable to read using 'parseCanonicalJSON'. So this is suitable to use for producing output that has to be later hashed or otherwise checked.

See the API docs on Hackage.

This package has been extracted from the hackage-security package where canonical JSON is used for all the signed TUF files, such as the root keys file, etc. As you can see from that, canoncal JSON allows keeping JSON files in a human readable pretty-printed form, and still allows verifying signatures. In particular this demonstrates the use of embedded signatures, where the root.json both contains a body value and multiple signatures of that body all within the same file. This is because canoncal JSON is about hashes for JSON values, not serialised JSON text.