Metadata
1 maintainer
Release files for mkdocs-simple 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 | |
|---|---|---|---|---|
| mkdocs_simple-0.0.1.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mkdocs_simple-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.8 kB
Release files / mkdocs_simple-0.0.1.tar.gz
| Download URL | mkdocs_simple-0.0.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b780dc52c3b4469e57f237e16b8f6751d6d67160ddd2e850f4476ca6277b03c
|
|
BLAKE2b-256 checksum How to use checksums |
f491a8ccbb32fb3b7c6b9b5513178b4c14c948ba239ba86db0f700b0cf507790
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.11.1 Darwin/22.1.0
|
Release files / mkdocs_simple-0.0.1-py3-none-any.whl
| Download URL | mkdocs_simple-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
517ee52036ed8c134fe8e8265648286f615d4583906e228ad482a9ccf37a68c0
|
|
BLAKE2b-256 checksum How to use checksums |
dda3a38274925202baf748042d523984e9aa202d088560b2e2fe62432a0c6532
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.11.1 Darwin/22.1.0
|
Security for mkdocs-simple 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.
