2 files were added to this release more than 14 days after its initial publication. Inspect the release files before installing.
1 maintainer
Metadata
1 maintainer
Release files for barbell 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Files added late
2 files were uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| barbell-0.2.1.tar.gz | 23.6 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| barbell-0.2.1-py3.5.egg | Legacy Egg format | - | - | Details |
| barbell-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 74.9 kB
Release files / barbell-0.2.1.tar.gz
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | barbell-0.2.1.tar.gz |
|---|---|
| Size | 23.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d203628cf791571d34702f198621f91a345cdcf3e99f2b02e22c6c4bee53563
|
|
BLAKE2b-256 checksum How to use checksums |
066d573b9d52688b69b58e5f60a95a223e4fa4e8df026633a4e52e4834076a3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/42.0.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.5.2
|
Release files / barbell-0.2.1-py3.5.egg
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | barbell-0.2.1-py3.5.egg |
|---|---|
| Size | 33.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
85d769a4253d54b5db42b7008a9d4e0b806bd72a87ed720bf7015e0ef643a093
|
|
BLAKE2b-256 checksum How to use checksums |
1b11440d80c4f5a97f09650d56fc4c0e6971b4821050729a05b509ad68e517cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/42.0.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.5.2
|
Release files / barbell-0.2.1-py3-none-any.whl
| Download URL | barbell-0.2.1-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c80211073bd7f0a8509f7cb6813fd138bbb8122eefbb657da60830264cc5e1ec
|
|
BLAKE2b-256 checksum How to use checksums |
ec190c40f87521ac54b7b7257d5761e37eac5d9350b885dedc6184676c97ffee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.5.2
|
Security for barbell 0.2.1
Upload timing
Files added late
2 files were uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.
