The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for admmcoml 0.1.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 | |
|---|---|---|---|---|
| admmcoml-0.1.0.tar.gz | 198.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| admmcoml-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 398.3 kB
Release files / admmcoml-0.1.0.tar.gz
| Download URL | admmcoml-0.1.0.tar.gz |
|---|---|
| Size | 198.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
386b91b2dbe13b181b0d78e5c17bba97ecbd81e67cc8d22409ea357cd89f75a1
|
|
BLAKE2b-256 checksum How to use checksums |
a1fa0486e9787996726b5c98b6a83b7f07caf5b17e8a844ba944424f9140fcba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.12
|
Release files / admmcoml-0.1.0-py3-none-any.whl
| Download URL | admmcoml-0.1.0-py3-none-any.whl |
|---|---|
| Size | 200.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71e70f098d4504e7ec51fa00989eb3220f1c1ce2b8b0add2b8b970d8aca11781
|
|
BLAKE2b-256 checksum How to use checksums |
f29b452030782b77cc3911c43fc5046dd09e9fc18831340f1109be28064c9b21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.12
|
Security for admmcoml 0.1.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.
