Metadata
Release files for dir2html 0.2.2
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 | |
|---|---|---|---|---|
| dir2html-0.2.2.tar.gz | 83.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dir2html-0.2.2-py3.6.egg | Legacy Egg format | - | - | Details |
Total release size: 171.3 kB
Release files / dir2html-0.2.2.tar.gz
| Download URL | dir2html-0.2.2.tar.gz |
|---|---|
| Size | 83.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9758cc1f610a7e88f2b90b657dddc4e8babf57241f0d659f67b5be8b31729ead
|
|
BLAKE2b-256 checksum How to use checksums |
5533d78ba86b4dac96c8149025d57d22a77ecdd12b2627fd4562a094afcd2d30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Release files / dir2html-0.2.2-py3.6.egg
| Download URL | dir2html-0.2.2-py3.6.egg |
|---|---|
| Size | 88.0 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
62aac0f264c2eb6e1ad20edf965e06b286ee95136d87594a6d8821e2710a89bb
|
|
BLAKE2b-256 checksum How to use checksums |
554b68278b631227b1a9ea8c3439070fa18674df5bba40d3d646e0f2ac2189ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/39.0.1 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7
|
Security for dir2html 0.2.2
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.