The author of this package has not provided a project description
Metadata
Release files for bbo-pysisplit 1.0.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 | |
|---|---|---|---|---|
| bbo-pysisplit-1.0.0.tar.gz | 12.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bbo_pysisplit-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.2 kB
Release files / bbo-pysisplit-1.0.0.tar.gz
| Download URL | bbo-pysisplit-1.0.0.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
faca524359aad42de7121d854dd105f61c64b20cbae89db59d6a57d5a0d6e830
|
|
BLAKE2b-256 checksum How to use checksums |
a6f3fd76051309fab7a99a5ee49310d0fc32ec00e88b226a0da42647ea38a26b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Release files / bbo_pysisplit-1.0.0-py3-none-any.whl
| Download URL | bbo_pysisplit-1.0.0-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbefd297d0018d765aec5f68eb2cc64ffbc2f7fb381004ae28deb319a89ec775
|
|
BLAKE2b-256 checksum How to use checksums |
8caede02860c0256757eb1287faf1e9b308a4775363b17745731a1aaa94a0d5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for bbo-pysisplit 1.0.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.