The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for axanexa-moncli 3.0.1
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 | |
|---|---|---|---|---|
| axanexa_moncli-3.0.1.tar.gz | 66.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axanexa_moncli-3.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 141.3 kB
Release files / axanexa_moncli-3.0.1.tar.gz
| Download URL | axanexa_moncli-3.0.1.tar.gz |
|---|---|
| Size | 66.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb70e73880311a6cfabd400956a0a00a620755f4959d5fac98627c29b0e2879c
|
|
BLAKE2b-256 checksum How to use checksums |
2f94e4ef6fbb1017d516cbed109c78d15ac284b505240307c7356771ef4cc665
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / axanexa_moncli-3.0.1-py3-none-any.whl
| Download URL | axanexa_moncli-3.0.1-py3-none-any.whl |
|---|---|
| Size | 75.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b701da67128f56e926b086561b4fba76ec405109f5f37a3c8d8505791a796c3a
|
|
BLAKE2b-256 checksum How to use checksums |
488d3fa845bd67985d69d9146d9e30255a259a38e9297cddf16db00afd377b34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for axanexa-moncli 3.0.1
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.
