The author of this package has not provided a project description
Metadata
Release files for renku-graph-vis 0.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 | |
|---|---|---|---|---|
| renku-graph-vis-0.0.4.tar.gz | 20.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| renku_graph_vis-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.7 kB
Release files / renku-graph-vis-0.0.4.tar.gz
| Download URL | renku-graph-vis-0.0.4.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d639805aa39436e100aa00397f0bb3b6b7725eef1d1f947d0aca66266d61fa03
|
|
BLAKE2b-256 checksum How to use checksums |
d990d8357a1181d8a56f0cffdf77fd157c4ec192d4461213b3e4a8e7df5654f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / renku_graph_vis-0.0.4-py3-none-any.whl
| Download URL | renku_graph_vis-0.0.4-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0906384e98a0037c7804d4b64f9e1b3818f2c428d2647e4e445c33d5b28457d
|
|
BLAKE2b-256 checksum How to use checksums |
e7354c2f29043c2eee9b27ad436d9aff34baccd21ea5805e9f3bd1406b38f4db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for renku-graph-vis 0.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.