The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for augmolino 0.0.5
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 | |
|---|---|---|---|---|
| augmolino-0.0.5.tar.gz | 20.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| augmolino-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.1 kB
Release files / augmolino-0.0.5.tar.gz
| Download URL | augmolino-0.0.5.tar.gz |
|---|---|
| Size | 20.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32e6f032c91b6c74a1fce874ce86b9d7697fe62681dc37d21a745d984e53d7fd
|
|
BLAKE2b-256 checksum How to use checksums |
440900d43724d9c7b119e1e0cd0ea18a6edecc17aa9fc5dd3f1164f3e7e3258e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.8.0
|
Release files / augmolino-0.0.5-py3-none-any.whl
| Download URL | augmolino-0.0.5-py3-none-any.whl |
|---|---|
| Size | 19.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5fb72375260db8c2af23cc1f2cf49a6cec3d077b2cc6df1f9c277cd6ca61b22
|
|
BLAKE2b-256 checksum How to use checksums |
556ab268a26731f52542388ff603852044cfaa9f0619e7a5b249202f08dc95b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.8.0
|
Security for augmolino 0.0.5
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.
