The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for AutoGGUF 1.8.1
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 | |
|---|---|---|---|---|
| autogguf-1.8.1.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| AutoGGUF-1.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.2 kB
Release files / autogguf-1.8.1.tar.gz
| Download URL | autogguf-1.8.1.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d3ef9d9e7d135a055e16534636e174210e88cfe4cdedff1d2be899be2aab7f8
|
|
BLAKE2b-256 checksum How to use checksums |
477e2526f89cbb0c40de92971516de70391d873a21307bae5f11d342f6019c58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Release files / AutoGGUF-1.8.1-py3-none-any.whl
| Download URL | AutoGGUF-1.8.1-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d15b738a63c93c45a6d4559f40715380bc9877ba0e9c4ca12912f830badf87c
|
|
BLAKE2b-256 checksum How to use checksums |
82e25622e1ee8934c6f2b1f4e60db09a516f9024d65d3b90d3e52706f0d16259
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.1
|
Security for AutoGGUF 1.8.1
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.
