1 maintainer
Metadata
1 maintainer
Release files for feishu-to-excel 0.0.4
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 | |
|---|---|---|---|---|
| feishu_to_excel-0.0.4.tar.gz | 7.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| feishu_to_excel-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.7 kB
Release files / feishu_to_excel-0.0.4.tar.gz
| Download URL | feishu_to_excel-0.0.4.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5cc3549470fa348a8b400631e37f19b1c38922e156c25c06a9571b1e1da4fdb
|
|
BLAKE2b-256 checksum How to use checksums |
3b9a0bbf0762ee3ed089ec0c00292f23e96a897e499b9e8d79c0b3d258bbe81c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.5
|
Release files / feishu_to_excel-0.0.4-py3-none-any.whl
| Download URL | feishu_to_excel-0.0.4-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a46f179961b469f35acdba16f8c65118497ff74016da2ec9d432c65e9cded011
|
|
BLAKE2b-256 checksum How to use checksums |
66b14ceabdebf5f03cd2f5d10a7187665afc58343b97e31a36e6f31c4363ba6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.5
|
Security for feishu-to-excel 0.0.4
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.
