The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for meta_sphinx 0.1.8
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 | |
|---|---|---|---|---|
| meta_sphinx-0.1.8.tar.gz | 97.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| meta_sphinx-0.1.8-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 200.9 kB
Release files / meta_sphinx-0.1.8.tar.gz
| Download URL | meta_sphinx-0.1.8.tar.gz |
|---|---|
| Size | 97.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0369f7c2a036049a67316769b29ccee87c8541227725a88b1868feb10ae8385a
|
|
BLAKE2b-256 checksum How to use checksums |
3b8801ee343a4da1770943f61d50e6df3479a933bde60bd707987209e872a13e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.22.0
|
Release files / meta_sphinx-0.1.8-py2.py3-none-any.whl
| Download URL | meta_sphinx-0.1.8-py2.py3-none-any.whl |
|---|---|
| Size | 102.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7af4e7801377a051b69b96829c91c19328c28ce33968fecb213923c6e80d8f0e
|
|
BLAKE2b-256 checksum How to use checksums |
57a4882e08fad697686dd3c1523490095ce8542a2fd67be5b4113873f7ce08ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.22.0
|
Security for meta_sphinx 0.1.8
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.
