1 maintainer
Metadata
1 maintainer
Release files for autoannotate-cv 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 | |
|---|---|---|---|---|
| autoannotate_cv-0.0.1.tar.gz | 475 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoannotate_cv-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / autoannotate_cv-0.0.1.tar.gz
| Download URL | autoannotate_cv-0.0.1.tar.gz |
|---|---|
| Size | 475 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
29bc45ce2c92a18e805ec484d2ef3a404ee901ce76e11e6b94bca0cb98e4ba77
|
|
BLAKE2b-256 checksum How to use checksums |
f65dd28514fb58b8deff674d5acf59a3b4efd6a087fc98e24656b85879de4ec0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.2
|
Release files / autoannotate_cv-0.0.1-py3-none-any.whl
| Download URL | autoannotate_cv-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e86e24a6a3d80ade691d8b655fe830d90f904b4cb4e740174495b466a0caf030
|
|
BLAKE2b-256 checksum How to use checksums |
3f12ecf4c32330451a0e10b356fc2d412ea5498087b050ddf32ee6346f48a7dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.2
|
Security for autoannotate-cv 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.
