Metadata
Release files for sphinx-pydata-theme 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 | |
|---|---|---|---|---|
| sphinx_pydata_theme-0.1.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinx_pydata_theme-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 kB
Release files / sphinx_pydata_theme-0.1.0.tar.gz
| Download URL | sphinx_pydata_theme-0.1.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c2c8916787ba12c5101cd47f4d1ba160178312f00a7aba2a038287b3e580100
|
|
BLAKE2b-256 checksum How to use checksums |
91f2e051b6c13a21cfcfd9075c24d0b27864f4dcd9f170b896c45027c7768841
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / sphinx_pydata_theme-0.1.0-py3-none-any.whl
| Download URL | sphinx_pydata_theme-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c3a370a43c5c36d9d0f61be09b5ddf93cf088772b0863e90ec11ab1b443e2c1
|
|
BLAKE2b-256 checksum How to use checksums |
8fbef39e193e8b57632c71584a7ece90b39ce4b39255c217103a3ffce439c1e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for sphinx-pydata-theme 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.