The author of this package has not provided a project description
Metadata
Release files for crdt 0.0.1
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 | |
|---|---|---|---|---|
| crdt-0.0.1.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| crdt-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.4 kB
Release files / crdt-0.0.1.tar.gz
| Download URL | crdt-0.0.1.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1b13f1ac6f0683a25a09f908b66a8afd11e5c4f2ce258cc7b352db941c15040
|
|
BLAKE2b-256 checksum How to use checksums |
79cc5725e85323c01f3263457bd572b9ddd888abf90c149045070841ec77bbb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.1 CPython/3.10.7 Linux/5.10.0-19-amd64
|
Release files / crdt-0.0.1-py3-none-any.whl
| Download URL | crdt-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
def945155046d2408128abfe4bed0b2a2d20bc3f5ff1a65f0219e2a792748804
|
|
BLAKE2b-256 checksum How to use checksums |
3871291c832e045f6dac492d535c7dd8851913daeed509c379cb8b72c4efbb2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.1 CPython/3.10.7 Linux/5.10.0-19-amd64
|
Security for crdt 0.0.1
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.