The author of this package has not provided a project description
Metadata
Release files for ffmpeg-data-v5 4.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 | |
|---|---|---|---|---|
| ffmpeg_data_v5-4.6.tar.gz | 404.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ffmpeg_data_v5-4.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 827.1 kB
Release files / ffmpeg_data_v5-4.6.tar.gz
| Download URL | ffmpeg_data_v5-4.6.tar.gz |
|---|---|
| Size | 404.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2106d059dc750c67f5fbb1c91699fc622e1d5077897c414656e98570f81f169a
|
|
BLAKE2b-256 checksum How to use checksums |
abd85a2b65454fdccbafd0424a734379a01bd6c1edd473e912cbaff7f8312649
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / ffmpeg_data_v5-4.6-py3-none-any.whl
| Download URL | ffmpeg_data_v5-4.6-py3-none-any.whl |
|---|---|
| Size | 422.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e82e81b47ebd00c21dee5b97e99b7d8332b9a8ca4fdebf31fc0bf9bf1677845
|
|
BLAKE2b-256 checksum How to use checksums |
669750dc8d33d095cce145ec61ac55b37fac4609543d5506d3efdf93dec7c133
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for ffmpeg-data-v5 4.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.