The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for shirobako 0.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 | |
|---|---|---|---|---|
| shirobako-0.0.0.tar.gz | 719 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shirobako-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / shirobako-0.0.0.tar.gz
| Download URL | shirobako-0.0.0.tar.gz |
|---|---|
| Size | 719 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27fbf4da97051e82f7209dcd99a2f5893b9fd3ddce56bd90dc3387e5771f86a1
|
|
BLAKE2b-256 checksum How to use checksums |
1eedebbf770b27cebfc4e33fd5217769fcac7f83e7172569345cbbc5207a6fc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / shirobako-0.0.0-py3-none-any.whl
| Download URL | shirobako-0.0.0-py3-none-any.whl |
|---|---|
| Size | 970 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a68c54e5149b7cbf5a688fdef253c9ca3a36428909f400e5292fec66a1700a99
|
|
BLAKE2b-256 checksum How to use checksums |
f85e5df40fecdd1e22a5450cebdd59a1de6a9a11121f9c2320018b3369fdae36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for shirobako 0.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.
