Repository navigation
v0.1.1
v0.1.1
The first published release of canonprims: the RFC 8785 JSON
Canonicalization Scheme (jcs/rfc8785) in two independent implementations,
Rust and pure Go, gated against one conformance corpus.
A v0.1.0 tag exists but was never released. Its tag workflow looked up the
tag with an anonymous request, which cannot read a private repository, so it
stopped before building anything. 0.1.1 looks the tag up with the workflow's
read-only job token and carries the same library, corpus and command.
What it ships
- Rust crates
canonprims-core(schemes, refusal codes, limits, digests)
andcanonprims-json(RFC 8785 over a strict I-JSON loader), published to
crates.io. Minimum supported Rust 1.88. - Go module
github.com/3leaps/canonprims, packagecanon, standard
library only and cgo-free, on Go 1.21 or later. - The
canoncommand (canon jcs [--check] [--digest] FILE|-,
canon info,canon version [--extended]) for linux amd64/arm64, darwin
arm64 and windows amd64/arm64.
Both implementations refuse input outside the I-JSON domain with the same
nine normative codes (invalid_json, invalid_utf8, duplicate_member,
lone_surrogate, noncharacter, non_finite_number,
integer_outside_binary64, too_deep, too_large), never repair it, and
take explicit limits on every call. canon jcs --check adds not_canonical
for well-formed input that is not already canonical. The
defaults are 16 MiB of input, depth 128, 1,048,576 members per object and
16 MiB per string.
Conformance
- Corpus
conformance/canonical-json/v0, 180 cases.
MANIFEST.jsonsha256:
de3ac543580ddb90f7e3a6e72239097274d3635ea783f302a9260b5a7d0c8d90. - Expected bytes are written by hand or taken from RFC 8785, never generated
by either implementation. The expected bytes of the file-based accept cases
are also checked by two independent witnesses: ECMAScriptJSON.stringify
(all 63) and a separate Python checker (crucible v0.2.2,
scripts/rfc8785-canonicalize.py; 58 of them, as it cannot witness the five
ES6-spelled integers). Refusal cases and generated input are not witnessed;
they are covered by the Rust/Go agreement below. - Rust and Go agree byte for byte on the corpus and on generated input:
crosscheck seeds20261022and20261023, 5000 inputs each, on every
native CI cell.
Verification
canon canonicalizes and digests; it verifies no signatures, so it embeds no
key. To verify this release, check the signed tag v0.1.1 and the signed
checksum manifests against the public pins committed in the tagged commit
(docs/security/); see docs/security/README.md.