The author of this package has not provided a project description
Metadata
Release files for izihawa-ipfs-api 1.0.7
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 | |
|---|---|---|---|---|
| izihawa-ipfs-api-1.0.7.tar.gz | 3.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| izihawa_ipfs_api-1.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.5 kB
Release files / izihawa-ipfs-api-1.0.7.tar.gz
| Download URL | izihawa-ipfs-api-1.0.7.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72c988b700e2cd9b088af74e3a38978ee95c793f15e86c1572509ecc443cb400
|
|
BLAKE2b-256 checksum How to use checksums |
3eedaf83072902e81d81064f786bbeda7cf138393e4097ecafa232f1dbb2660f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Release files / izihawa_ipfs_api-1.0.7-py3-none-any.whl
| Download URL | izihawa_ipfs_api-1.0.7-py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
50ff8eada5a8abec17b2fe74d50f8c0b637a197c944fe0e378ee4300a2d91dfa
|
|
BLAKE2b-256 checksum How to use checksums |
6e9070634ded9d731c20ada98a4ea00d3d85986338811ffc61f3ae46242c4fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.12
|
Security for izihawa-ipfs-api 1.0.7
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.