The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for gixy 0.1.21
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 | |
|---|---|---|---|---|
| gixy-0.1.21.tar.gz | 58.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gixy-0.1.21-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 110.8 kB
Release files / gixy-0.1.21.tar.gz
| Download URL | gixy-0.1.21.tar.gz |
|---|---|
| Size | 58.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e39c87401c73d33cd8965324caa3e1778ef22ed7ade179b459a3493bdfe0f88a
|
|
BLAKE2b-256 checksum How to use checksums |
990b8f044be05492e06311d01148e5d1a5c18e7b8cb9126f7cc14d0e1375a53d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Release files / gixy-0.1.21-py2.py3-none-any.whl
| Download URL | gixy-0.1.21-py2.py3-none-any.whl |
|---|---|
| Size | 52.7 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
55be805e0582ac95540f49ea7f80b2de0b5304cb63edd22e1e6520d18f3c184b
|
|
BLAKE2b-256 checksum How to use checksums |
cba278fb862613cdb55fdb9b89ca8b170f257e6fdef8f13aef240ef6df95a9c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Security for gixy 0.1.21
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.
