Your package description goes here.
1 maintainer
Metadata
1 maintainer
Release files for auto-clean-data 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 | |
|---|---|---|---|---|
| auto_clean_data-0.1.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auto_clean_data-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.0 kB
Release files / auto_clean_data-0.1.tar.gz
| Download URL | auto_clean_data-0.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ed9b0b8012b0be13ff95f11adcfa4c84048ce10bce4f719ba5bb8804aad3d85
|
|
BLAKE2b-256 checksum How to use checksums |
84bc0ba0fd10fccda7be0cc475a03397dc7d1685f3046001e2df339610632823
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / auto_clean_data-0.1-py3-none-any.whl
| Download URL | auto_clean_data-0.1-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3e78dc915bbbe45c650808eb373b84f9650ba4a7d5d460deba280d8142117d2
|
|
BLAKE2b-256 checksum How to use checksums |
ee0c51739ae9c1a478d81ed0aebca736fe31c8c711bebe791cddcc0ddb8765aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for auto-clean-data 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.
