The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mariekondo 0.0.3
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 | |
|---|---|---|---|---|
| mariekondo-0.0.3.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mariekondo-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.2 kB
Release files / mariekondo-0.0.3.tar.gz
| Download URL | mariekondo-0.0.3.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24b8c449e393bb3b5cd4ba7927c6050e50b130cae41c00ffef63a862d2a1af1b
|
|
BLAKE2b-256 checksum How to use checksums |
0da86aa404fe8e42b92965baeea98d7d2a6b4221b61c96f33ce07e82da64efb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / mariekondo-0.0.3-py3-none-any.whl
| Download URL | mariekondo-0.0.3-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5e9b0bbb50bc8fb9cfc07bbd9863359400f7059886f41fdde992964bd84576a
|
|
BLAKE2b-256 checksum How to use checksums |
27df59839d85b0681548b40d25984ad871f98d10eb520552ce798eddfc5b0665
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for mariekondo 0.0.3
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.
