The author of this package has not provided a project description
Metadata
Release files for torrent-gguf 0.1.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 | |
|---|---|---|---|---|
| torrent_gguf-0.1.0.tar.gz | 12.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| torrent_gguf-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.4 kB
Release files / torrent_gguf-0.1.0.tar.gz
| Download URL | torrent_gguf-0.1.0.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
99f94f41ab96bdfd6047897ce2dd309055c62e7e59658c1d19b170e859558d0c
|
|
BLAKE2b-256 checksum How to use checksums |
a0a021d2d722b2d320a1b1aacbc42dc23c6315749bf5f4687e316f6d59bc9f41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / torrent_gguf-0.1.0-py3-none-any.whl
| Download URL | torrent_gguf-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a6754b0e6d07cba2285b85d4cc843985b1a312aedc59269f602e2e1aa52cb15
|
|
BLAKE2b-256 checksum How to use checksums |
c66b2dc21230e9609affc1656ec5163b6ccdeec64696ef845b3527211899ae36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for torrent-gguf 0.1.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.