asnkitrt
Encodes and decodes ASN.1 using compiled specifications: .asni files produced by the asnkitcc compiler. It never parses ASN.1 and has no dependencies.
>>> import asnkitrt
>>> foo = asnkitrt.load_asni_file('foo.asni', 'uper')
>>> encoded = foo.encode('Question', {'id': 1, 'question': 'Is 1+1=3?'})
>>> foo.decode('Question', encoded)
{'id': 1, 'question': 'Is 1+1=3?'}The supported codecs are BER, DER, GSER, JER, OER, PER, UPER and XER. Each is imported only when used. A Rust runtime with the same behavior, and a WebAssembly one for browsers and Node.js, live in the same repository, which also documents the formats and the known limitations.
An .asni file can carry a nonce, be bound to a string, and be signed and encrypted. Such a file only loads when the caller says what to expect. Signed and encrypted files need the cryptography package, which is an optional extra:
pip install asnkitrt[signing]
pip install asnkitrt[encryption]License
MIT. The compiler, asnkitcc, is Apache-2.0, and an application that only uses asnkitrt does not depend on it.
1 maintainer
Metadata
1 maintainer
Release files for asnkitrt 1.2.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 | |
|---|---|---|---|---|
| asnkitrt-1.2.0.tar.gz | 107.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asnkitrt-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 231.8 kB
Release files / asnkitrt-1.2.0.tar.gz
| Download URL | asnkitrt-1.2.0.tar.gz |
|---|---|
| Size | 107.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
49654f4ece9ff11a65d61c03ffe0574c162cd0432bf47eaf1ef61e6fa3fe9538
|
|
BLAKE2b-256 checksum How to use checksums |
b4e01535639433d99050efdbe96107ae4052f296c8fab6b546cca582fde7d98c
|
| 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 18, 2026.
Transparency logRelease files / asnkitrt-1.2.0-py3-none-any.whl
| Download URL | asnkitrt-1.2.0-py3-none-any.whl |
|---|---|
| Size | 124.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92f22aac86878a8e26f39b99d41858e39ceab6d1fb204778300e26b44e2b236b
|
|
BLAKE2b-256 checksum How to use checksums |
c69ba7d0b56707e475e839730aeb4f7b71345c58d9738650cada97cab9d06b34
|
| 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 18, 2026.
Transparency logSecurity for asnkitrt 1.2.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 2 files in this release have been uploaded with provenance metadata.
Attestation for asnkitrt-1.2.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 18, 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.
