The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autogit-ui 0.1.3
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 | |
|---|---|---|---|---|
| autogit_ui-0.1.3.tar.gz | 8.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autogit_ui-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.8 kB
Release files / autogit_ui-0.1.3.tar.gz
| Download URL | autogit_ui-0.1.3.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c655030ccc980b6bf29516a00417c8abeb9e5811a744e81291e630ca0f55825a
|
|
BLAKE2b-256 checksum How to use checksums |
d344522f17e4ba01a5602cc895a6bd3fcef4b6091a352b729b675628bbfc32dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Release files / autogit_ui-0.1.3-py3-none-any.whl
| Download URL | autogit_ui-0.1.3-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33f4f367e867d7436fe876e5ca6b0d79d5178a09a3ae71d61f791c8bd6e50bbf
|
|
BLAKE2b-256 checksum How to use checksums |
ecae63af93c06f541935e0b5b8cbf7a96b9dd3c2149e38dce6577c841192c78e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.0
|
Security for autogit-ui 0.1.3
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.
