Metadata
Release files for trytond-account-statement 8.2.0
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 | |
|---|---|---|---|---|
| trytond_account_statement-8.2.0.tar.gz | 74.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trytond_account_statement-8.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 211.3 kB
Release files / trytond_account_statement-8.2.0.tar.gz
| Download URL | trytond_account_statement-8.2.0.tar.gz |
|---|---|
| Size | 74.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
906ca96380ce3dbd3055bdb43cf8a3c9d760e69da933cb22f95ad3146d43e7ff
|
|
BLAKE2b-256 checksum How to use checksums |
0a420fad7fe8e4c6a656f136e6bca8016a2470448ba7b389648ce01e8285b4b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / trytond_account_statement-8.2.0-py3-none-any.whl
| Download URL | trytond_account_statement-8.2.0-py3-none-any.whl |
|---|---|
| Size | 136.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9268306f3f77bbeea294d20e7290de8b016c6f9893e8b14f0e67edf67261af9
|
|
BLAKE2b-256 checksum How to use checksums |
3be26237f82ca01ccc4e77820b296aa692ad93d8511443ef593e2cdee9ec6c0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for trytond-account-statement 8.2.0
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.
