1 maintainer
Metadata
1 maintainer
Release files for invoice-parser 0.0.6
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 | |
|---|---|---|---|---|
| invoice_parser-0.0.6.tar.gz | 15.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| invoice_parser-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.7 kB
Release files / invoice_parser-0.0.6.tar.gz
| Download URL | invoice_parser-0.0.6.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
03ff83f25ebdfac2d9d4a51494b00cb25c69b1a2cdc8c1925d35cfdbf974c2f0
|
|
BLAKE2b-256 checksum How to use checksums |
56562122d290f5e92e1741ae1bececc6b418d7e00b0352c972f5d4e3efb14b6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / invoice_parser-0.0.6-py3-none-any.whl
| Download URL | invoice_parser-0.0.6-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6950c9cc50e1b6c7ff761341df26a6e94d40061a3688de9096a4f045d74c6101
|
|
BLAKE2b-256 checksum How to use checksums |
4a79036cf1e401f8eeeadfbf5642a39cbdece9e69c7224c2211d060e1451ad43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for invoice-parser 0.0.6
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.
