The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for datacontract 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 | |
|---|---|---|---|---|
| datacontract-0.1.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datacontract-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / datacontract-0.1.0.tar.gz
| Download URL | datacontract-0.1.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4a73d205743bbf79603b05d80654feb9a2fed4f21fd3b57ffa86069dd1ce61c
|
|
BLAKE2b-256 checksum How to use checksums |
a78b8618b261f47ab3a503f5b920fa4d8db511f9005b0c91e0ba639d2c355a8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.10.12
|
Release files / datacontract-0.1.0-py3-none-any.whl
| Download URL | datacontract-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30973109208e4a97652871ab5ccb9242264fbb0333b0635c61c15707be02f846
|
|
BLAKE2b-256 checksum How to use checksums |
5f3deeb4132d774a7eec0df9601f672017c96f7f6cecefd07fcc3b3de2542ebc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.10.12
|
Security for datacontract 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.
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.
