Metadata
Release files for jsphinx 0.0.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 | |
|---|---|---|---|---|
| jsphinx-0.0.1.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jsphinx-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.8 kB
Release files / jsphinx-0.0.1.tar.gz
| Download URL | jsphinx-0.0.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03d20991c40f2ca2eecfb86daae4734b2166371e50703f4a44e315e5deb43b8e
|
|
BLAKE2b-256 checksum How to use checksums |
ea2cbcffed7159263fd5b61f638cd2087dae9f8646d1efb0c4736b3f0070c172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.8.12
|
Release files / jsphinx-0.0.1-py3-none-any.whl
| Download URL | jsphinx-0.0.1-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7bd442410c49492aee9b00469904ba58a5a320982d6aef744575f3a61c82d091
|
|
BLAKE2b-256 checksum How to use checksums |
4900ae8d62e8e7eda06679880d4a08f6e92785e0192a417a841b135f2d676db0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.8.12
|
Security for jsphinx 0.0.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.