The author of this package has not provided a project description
Metadata
Release files for aea-cli-ipfs 1.0.4
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 | |
|---|---|---|---|---|
| aea-cli-ipfs-1.0.4.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aea_cli_ipfs-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.0 kB
Release files / aea-cli-ipfs-1.0.4.tar.gz
| Download URL | aea-cli-ipfs-1.0.4.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c16b71a96c2563808ecfacfa815126f81351418619f7a3be1c17b3ea72dd14cc
|
|
BLAKE2b-256 checksum How to use checksums |
5092b7b4b7a08ea272b41f473e6079a5ae47341b1c5dfded2074a4eac345d2a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.0
|
Release files / aea_cli_ipfs-1.0.4-py3-none-any.whl
| Download URL | aea_cli_ipfs-1.0.4-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac53e2ea80b3fd028d8ec4f22eee3e251e38d22a3d69b46b1ff18489eb017201
|
|
BLAKE2b-256 checksum How to use checksums |
48011e9d44bd476d22d4fbe8647c82446e10333f63ccbf1f46be2a992af41cd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.0
|
Security for aea-cli-ipfs 1.0.4
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.