Metadata
Release files for trytond-stock-supply 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_stock_supply-8.2.0.tar.gz | 38.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trytond_stock_supply-8.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 112.8 kB
Release files / trytond_stock_supply-8.2.0.tar.gz
| Download URL | trytond_stock_supply-8.2.0.tar.gz |
|---|---|
| Size | 38.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e6b8b3abee9be8f384a8728917fcea85faf48e789e0f63060680f33c5a53fb5
|
|
BLAKE2b-256 checksum How to use checksums |
983ef9009b005791239b6b4b71fa7e1f8945d39fbf949ebd479ace345abedd44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / trytond_stock_supply-8.2.0-py3-none-any.whl
| Download URL | trytond_stock_supply-8.2.0-py3-none-any.whl |
|---|---|
| Size | 74.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18d5c031a5dd31c29bc84d62a05a0134ee8f6604f803218310f13c74fed3a14f
|
|
BLAKE2b-256 checksum How to use checksums |
929de6560767dadfd31c819b945461e18873a3ecf0a0e460db7c0c95a76934b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for trytond-stock-supply 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.
