The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for xlsx2csv 0.8.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 | |
|---|---|---|---|---|
| xlsx2csv-0.8.1.tar.gz | 215.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xlsx2csv-0.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 229.7 kB
Release files / xlsx2csv-0.8.1.tar.gz
| Download URL | xlsx2csv-0.8.1.tar.gz |
|---|---|
| Size | 215.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ecd6d2bc2426f2e432f4fdac12211e1976d3cbb65f9033e1eda65edda2045e3
|
|
BLAKE2b-256 checksum How to use checksums |
76e66a2dd0b201407148a1837c2f071ef41dee8bcda7666e518b260f79979788
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Release files / xlsx2csv-0.8.1-py3-none-any.whl
| Download URL | xlsx2csv-0.8.1-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c36c0295d64f231570479e514d6163ce135af3c431a1705b073230bedaef9f2
|
|
BLAKE2b-256 checksum How to use checksums |
82c065020392e59af0ecea73522167f2cc2dd755546e0b4a675eec726bc5cab2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for xlsx2csv 0.8.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.
