The author of this package has not provided a project description
3 maintainers
Metadata
3 maintainers
Release files for buildbot-pkg 4.3.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 | |
|---|---|---|---|---|
| buildbot_pkg-4.3.0.tar.gz | 5.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| buildbot_pkg-4.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.8 kB
Release files / buildbot_pkg-4.3.0.tar.gz
| Download URL | buildbot_pkg-4.3.0.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42933a779e508c0e2ed62708cfc5d23b78ba456436268d8ddbfd51786abdf57e
|
|
BLAKE2b-256 checksum How to use checksums |
891ea008cc08004bdda7fccb5c3bd0a7dd399d09755ceae975dd9add242748ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / buildbot_pkg-4.3.0-py3-none-any.whl
| Download URL | buildbot_pkg-4.3.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22fed283643db69051a5742f635e144eb9f5ff570bf255505e752c309867b6db
|
|
BLAKE2b-256 checksum How to use checksums |
3943dad2b47bf6ada3ce52aba4d4df915ae1263f1c5c79f67f3a8294c5ed07d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for buildbot-pkg 4.3.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.
