An implementation of RFC 7049 - Concise Binary Object Representation (CBOR).
CBOR is comparable to JSON, has a superset of JSON’s ability, but serializes to a binary format which is smaller and faster to generate and parse.
The two primary functions are cbor.loads() and cbor.dumps().
This library includes a C implementation which runs 3-5 times faster than the Python standard library’s C-accelerated implementanion of JSON. This is also includes a 100% Python implementation.
Metadata
Release files for cbor 1.0.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 | |
|---|---|---|---|---|
| cbor-1.0.0.tar.gz | 20.1 kB | Without provenance | Details |
Release files / cbor-1.0.0.tar.gz
| Download URL | cbor-1.0.0.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13225a262ddf5615cbd9fd55a76a0d53069d18b07d2e9f19c39e6acb8609bbb6
|
|
BLAKE2b-256 checksum How to use checksums |
9b9901c6a987c920500189eb74a291bd3a388e6c7cf85736bb6b066d9833315e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cbor 1.0.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.
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.