# exif_utils
1 maintainer
Metadata
1 maintainer
Release files for exif_utils 0.0.1
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 | |
|---|---|---|---|---|
| exif_utils-0.0.1.tar.gz | 3.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| exif_utils-0.0.1-py3.6.egg | Legacy Egg format | - | - | Details |
Total release size: 10.0 kB
Release files / exif_utils-0.0.1.tar.gz
| Download URL | exif_utils-0.0.1.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5be1e84e64ab7f143a626256d918ac41ce89c568f22da835e4bc528b85427fa
|
|
BLAKE2b-256 checksum How to use checksums |
89c5800a7b693de8e73414455668794789219fce6d8948d0512092ecebf5911e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Release files / exif_utils-0.0.1-py3.6.egg
| Download URL | exif_utils-0.0.1-py3.6.egg |
|---|---|
| Size | 6.9 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
39b05e148b2f8479fd2f4d158bc9e2e0b9ee131f88cfef0e8de9084a80bcb214
|
|
BLAKE2b-256 checksum How to use checksums |
68b0da90f4dbf5a3b0235fc8d177b69e39aeb5e7fe0ea774faf7afd72e9242cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.19.1 setuptools/39.1.0 requests-toolbelt/0.8.0 tqdm/4.26.0 CPython/2.7.15
|
Security for exif_utils 0.0.1
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.
