Metadata
1 maintainer
Release files for bryte 0.1.3
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 | |
|---|---|---|---|---|
| bryte-0.1.3.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bryte-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.4 kB
Release files / bryte-0.1.3.tar.gz
| Download URL | bryte-0.1.3.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
996ccf6e669ebc36f6e712c90d8cfb9dcae96bf502008b65b5a651e1fbd6427f
|
|
BLAKE2b-256 checksum How to use checksums |
6ebec5fbfe155c098f767bb55a6c0155e728e68b038b970f47192ffe83f3538a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.1 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.5
|
Release files / bryte-0.1.3-py3-none-any.whl
| Download URL | bryte-0.1.3-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca0f4744963341ff3493255974379ac0dc3da6602c558dbb3163f770665a0426
|
|
BLAKE2b-256 checksum How to use checksums |
767427256634ec8f7c20feffd17c2749f6cbbe33080fadafbca1e44eb3064cca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.18.1 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.5
|
Security for bryte 0.1.3
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.
