Release files for gfagui 1.0.0
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 | |
|---|---|---|---|---|
| gfagui-1.0.0.tar.gz | 56.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gfagui-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.8 kB
Release files / gfagui-1.0.0.tar.gz
| Download URL | gfagui-1.0.0.tar.gz |
|---|---|
| Size | 56.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae1e1177ee18dd42d9c97107573374a2f6bad7601174e3283b666a9ba7466140
|
|
BLAKE2b-256 checksum How to use checksums |
f1c736ef311686475f81cdb82d4671b9a82d3e49c901add4d15f6885919ec92e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.9
|
Release files / gfagui-1.0.0-py3-none-any.whl
| Download URL | gfagui-1.0.0-py3-none-any.whl |
|---|---|
| Size | 76.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a821e2e410e6652d6f08c76cac56a3a2e8216529cffe0f132220b275a64bf73
|
|
BLAKE2b-256 checksum How to use checksums |
08514f201c4aa1a235bb9d0e907abfc6152f07a42b36b7e772f6a2eb7721a43f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.7.9
|
Security for gfagui 1.0.0
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.
