1 maintainer
Metadata
1 maintainer
Release files for bcon 0.0.2
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 | |
|---|---|---|---|---|
| bcon-0.0.2.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bcon-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.6 kB
Release files / bcon-0.0.2.tar.gz
| Download URL | bcon-0.0.2.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
978cdab851c8239e1ddb14684be1961949cdddf7da3699a82a7a61aa8c97deb2
|
|
BLAKE2b-256 checksum How to use checksums |
a17ed808052e03e04fd1f85b4822f4ad9fe80569c44c1ff01c2b4962a9cc9f90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.0
|
Release files / bcon-0.0.2-py3-none-any.whl
| Download URL | bcon-0.0.2-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c42362ac527025a398c532e59ee37c1eea336379df822a60a38cbc83d2ae3ba3
|
|
BLAKE2b-256 checksum How to use checksums |
90af0ca73a86c3d1b1bafd066c18225b0d0d76ee89ca12f79ce86f2629596d4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.0
|
Security for bcon 0.0.2
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.
