jcs-admit
Python bindings for two Rust crates: jcs-admit
admits a JSON document on its raw bytes and returns its RFC 8785 canonical form, and
dsse signs and verifies DSSE envelopes, counting a
threshold over distinct keys.
pip install jcs-admit==0.1.0
import jcs_admit
jcs_admit.admit(b'{ "b": 1, "a": [1.0, 1e30] }') # b'{"a":[1,1e+30],"b":1}'
try:
jcs_admit.admit(b'{"a":1,"a":2}')
except jcs_admit.JcsError as e:
print(e.variant, e.fields) # DuplicateMember {'name': 'a', 'offset': 7}
import os
from jcs_admit import dsse
harness = dsse.Ed25519Signer(os.urandom(32), key_id="harness")
witness = dsse.Ed25519Signer(os.urandom(32), key_id="witness")
envelope = dsse.sign("application/vnd.in-toto+json", b'{"a":1}', [harness, witness])
verified = dsse.verify_threshold(envelope, [harness.verifier(), witness.verifier()], 2)
print(verified.payload_type, verified.payload, verified.accepted_keys)
The extension links jcs-admit 0.1.2 and dsse 0.1.3 unchanged. Every refusal is
a JcsError or a DsseError (both ValueError) whose variant and fields are
the Rust variant and fields. Each crate's documentation is the reference for what
it refuses and why: https://docs.rs/jcs-admit/0.1.2 and https://docs.rs/dsse/0.1.3.
Licensed under MIT or Apache-2.0, at your option.
1 maintainer
Metadata
1 maintainer
Release files for jcs-admit 0.1.0
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 |
|---|---|---|---|---|
| jcs_admit-0.1.0.tar.gz | 60.4 kB | With provenance | Details for jcs_admit-0.1.0.tar.gz |
Built distributions (wheels)
Total release size: 4.1 MB
Release files / jcs_admit-0.1.0.tar.gz
| Download URL | jcs_admit-0.1.0.tar.gz |
|---|---|
| Size | 60.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfe09e446a4a478334842eb7445bedfa61c512c1809e6f2a3be45409c878cae5
|
|
BLAKE2b-256 checksum How to use checksums |
afc5f8dace82f946b92008e25a08168e56d56a95aaac81cc7c2daa3e62a188ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-win_amd64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 416.9 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
9675034f3c555cde9361392a85e89e2bfbfedcc08eab9259503926ec2c24e46b
|
|
BLAKE2b-256 checksum How to use checksums |
2bb730563a659710fd703a30c98f06079cb2a543f99daf1e88c4d5bd7a416cb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-musllinux_1_2_x86_64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 783.9 kB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7b8295d9b3fd8873be79189456bfc199339c609e7479fae54bacc54494f771ec
|
|
BLAKE2b-256 checksum How to use checksums |
4ca7735b1fd0fb61d852a41a21a0699a48d8361bcedd4a84491b66e1a36a8a30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-musllinux_1_2_aarch64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 726.3 kB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
f850733f135414507610d1f7d703711958734cfa50f16fc236182f551ce24fdc
|
|
BLAKE2b-256 checksum How to use checksums |
507ac743597b9a0581b7f910d367903a494e7915269c15060ff3219acbcfd22e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 578.9 kB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
5506b8265d8c23759ddb0c6673d8f832a070503bbabcec01680b1f97527541b0
|
|
BLAKE2b-256 checksum How to use checksums |
93748520b59f3badae16248f3ec0c8634cc88a71384ac9c7141bcff93c81c7bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 549.6 kB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
c9342daeee4e623552ed24e7493066784e009a9d898a7beb0cdbf0ab0c83aba7
|
|
BLAKE2b-256 checksum How to use checksums |
56c216fecd94781e31b7a9356f9f048da1cd93363fd66329379d2fc03ae62b6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 495.9 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
82148364fe2a2aca3af1fbb33dce64e51c244959231c6c22a04d712212098aee
|
|
BLAKE2b-256 checksum How to use checksums |
c9ea3eb071e62b12a8030afffbcb025ba8b627538447f5037ad6139c2badeb35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / jcs_admit-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | jcs_admit-0.1.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 530.7 kB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
f1e8c5705579078cc5ff64bdb031f6a981f43db5a24fe7812504e1463003765d
|
|
BLAKE2b-256 checksum How to use checksums |
a0fef9d7850e50545a9d9abbb9c080e9a347f9eab2578c3d8d8f7845ba2c09e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for jcs-admit 0.1.0
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.
Full provenance
All 8 files in this release have been uploaded with provenance metadata.
Attestation for jcs_admit-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA 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.
