The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for trakt-hub 0.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 | |
|---|---|---|---|---|
| trakt_hub-0.0.0.tar.gz | 20.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trakt_hub-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.4 kB
Release files / trakt_hub-0.0.0.tar.gz
| Download URL | trakt_hub-0.0.0.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e09e0759d06d0d9bba39cdbe59389ffa034a1d18ed0034c712bb804b1f65f69
|
|
BLAKE2b-256 checksum How to use checksums |
5a5e425afd58185a63e587e7d457b51da1c54d61efce856bebacff54808ed7be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Release files / trakt_hub-0.0.0-py3-none-any.whl
| Download URL | trakt_hub-0.0.0-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8dc7fa5a739d98edfb6beb90f87f4333812fa48126644617b1f514f1fb13f99a
|
|
BLAKE2b-256 checksum How to use checksums |
b6432c2cfadcd7aa8368a6f9b6abff17ec0f480b845772f10754d67a44e4b51c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.0
|
Security for trakt-hub 0.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.
