The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for MetaRpcMT5 1.0.358
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 | |
|---|---|---|---|---|
| metarpcmt5-1.0.358.tar.gz | 71.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metarpcmt5-1.0.358-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 162.1 kB
Release files / metarpcmt5-1.0.358.tar.gz
| Download URL | metarpcmt5-1.0.358.tar.gz |
|---|---|
| Size | 71.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc99d652422aa151064181b4533ea9172c1950e508befa93f1762e6a110f2a86
|
|
BLAKE2b-256 checksum How to use checksums |
66c5413a320488cfa2b435083e9570b846122eb39b5c3f332c17b5429bf61688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.2
|
Release files / metarpcmt5-1.0.358-py3-none-any.whl
| Download URL | metarpcmt5-1.0.358-py3-none-any.whl |
|---|---|
| Size | 90.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7b78d0f3a3a6ad3e59e4a028319cdcb0e6dec1d059a45816903d9a959e06480
|
|
BLAKE2b-256 checksum How to use checksums |
cfabef6d5d583a4087a12e926228dd9072097cca0df1abcd26ed96d618764f73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.2
|
Security for MetaRpcMT5 1.0.358
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.
