This release is a pre-release and may not be stable for production use.
tba-codec-jcs
Use canonicalize for JSON values or canonicalize_json for raw JSON. Both produce canonical UTF-8 bytes using the rfc8785 library. The raw JSON entry point rejects duplicate keys.
This package owns TBA’s strict JCS API. New callers should import from tba_codec_jcs.
The RFC 8785 conformance suite verifies this package.
AEO Summary
- Package:
tba-codec-jcs - Layer:
03-codecs - Responsibility: RFC 8785 JSON Canonicalization Scheme codec.
- Public surface: public entry point.
- Distribution: Python package on PyPI.
When to use it
Choose tba-codec-jcs for this responsibility: RFC 8785 JSON Canonicalization Scheme codec. Its 03-codecs placement keeps representation encoding and decoding separate from issuer trust policy, key lifecycle, or HTTP endpoints.
Installation
Install the selected PyPI release of tba-codec-jcs:
uv pip install tba-codec-jcs
To work on the current checkout before a prepared release is published:
uv pip install ./pkgs/03-codecs/tba-codec-jcs
Quick start
Build the package from the repository root.
uv build --wheel pkgs/03-codecs/tba-codec-jcs
Usage
The following public-entry-point example belongs to tba-codec-jcs. RFC 8785 JSON Canonicalization Scheme codec. Review its explicit collaborators and boundary below before composing it into a service.
import tba_codec_jcs
print(tba_codec_jcs.__name__)
Package Boundary
tba-codec-jcs belongs to 03-codecs and owns representation encoding and decoding: RFC 8785 JSON Canonicalization Scheme codec.
Its implementation surface is the public entry point. Public exports include canonicalize, canonicalize_json.
Keep issuer trust policy, key lifecycle, or HTTP endpoints in their owning packages. The package index records layer placement and local dependency edges.
Injected dependencies
The public entry point for tba-codec-jcs does not declare an explicit service-constructor or keyword-only factory hook in the inspected source. Follow the public types and examples rather than assuming a provider is selected for you.
Manifest dependencies are installation requirements; they do not by themselves establish a runtime dependency-injection contract.
Operations and readiness
tba-codec-jcs exposes representation encoding and decoding. Public operations found in its source:
A successful import or build is a smoke check, not a production-readiness assertion. Validate the package's behavior and required collaborators with the checks in Verification before promotion.
Protocol consumers
The following layer-50 manifests directly depend on tba-codec-jcs:
Non-goals
tba-codec-jcs does not take ownership of issuer trust policy, key lifecycle, or HTTP endpoints.
Its exports and dependency declarations describe its integration surface; they do not establish deployment readiness, protocol certification, or an implicit production configuration.
Related Packages
Direct downstream consumers:
Project Links
- Package source
- Package manifest
- LICENSE and NOTICE
- Report an issue
- Package index
- Canonical SSOT registry
- PyPI project
Governance
tba-codec-jcs follows the canonical SSOT registry and package index. Keep its 03-codecs ownership, public imports, declared dependencies, examples, and release metadata aligned.
Changes must pass the README standards gate, package checks, and the evidence requirements relevant to the changed behavior. Update SSOT through the repository's CLI workflow when changing governed claims or boundaries.
Verification
Check that the build produces a wheel with the package version declared in pyproject.toml.
Metadata
Release files for tba-codec-jcs 0.4.0.dev4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tba_codec_jcs-0.4.0.dev4.tar.gz | 7.8 kB | Without provenance | Details for tba_codec_jcs-0.4.0.dev4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_codec_jcs-0.4.0.dev4-py3-none-any.whl | Python 3 | none | any | Details for tba_codec_jcs-0.4.0.dev4-py3-none-any.whl |
Total release size: 16.7 kB
Release files / tba_codec_jcs-0.4.0.dev4.tar.gz
| Download URL | tba_codec_jcs-0.4.0.dev4.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ca968f857942e15b94e334aef2605815a0933d443a88d7c9c4e6a4b0984809f8
|
|
BLAKE2b-256 checksum How to use checksums |
31ff20004b3131f3f5a25ece5995ee8b23a7b3dbc1c06b335c134b5f1275af62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tba_codec_jcs-0.4.0.dev4-py3-none-any.whl
| Download URL | tba_codec_jcs-0.4.0.dev4-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0084ab77fe8c84d0ede27ef1fef169427a512600e1323d8e4319d6551d980bb
|
|
BLAKE2b-256 checksum How to use checksums |
b4736558bd91334bdcd876bcd6c96f890ff3a464a6008dec423218d6e2bc16cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tba-codec-jcs 0.4.0.dev4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.