Metadata
Release files for ftrack-utils 3.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 | |
|---|---|---|---|---|
| ftrack_utils-3.2.0.tar.gz | 19.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftrack_utils-3.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.3 kB
Release files / ftrack_utils-3.2.0.tar.gz
| Download URL | ftrack_utils-3.2.0.tar.gz |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb75b4a768cb02a30252c759430029cad0d27c4b36ffb1afcd32089c87ce6671
|
|
BLAKE2b-256 checksum How to use checksums |
6fef7d4f7acfd13dd449560c40e1a95e969a2aaf719936a9faa038bdb2a23064
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Release files / ftrack_utils-3.2.0-py3-none-any.whl
| Download URL | ftrack_utils-3.2.0-py3-none-any.whl |
|---|---|
| Size | 29.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ac64b75aac9e09576c6c3de080df555c838374a0c3b4ac89a3213db88ab482b7
|
|
BLAKE2b-256 checksum How to use checksums |
5420c4138e42b907253dda83c494c661fdca156da97790d22b05dd55b53871ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for ftrack-utils 3.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.