The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for batch6-musigma 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 | |
|---|---|---|---|---|
| batch6_musigma-1.0.0.tar.gz | 3.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| batch6_musigma-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.7 kB
Release files / batch6_musigma-1.0.0.tar.gz
| Download URL | batch6_musigma-1.0.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46014fe402b459a4f4e7afd425acec530bf5f14a5d89aa02490c24f7022d1229
|
|
BLAKE2b-256 checksum How to use checksums |
bcb098c5681165fcba660c9c92fdbffaed888bce565f908aaff84ebe4a5bc34d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.7
|
Release files / batch6_musigma-1.0.0-py3-none-any.whl
| Download URL | batch6_musigma-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86892c4d9ccbbf45fd6dedef97cfb94696278474537bda25024010ad8ff00540
|
|
BLAKE2b-256 checksum How to use checksums |
9446797674a488536a6523d9e8149ff17ba58720c793ed99139aa75e09eac5ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.7
|
Security for batch6-musigma 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.
