The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for baseToImgX 1.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 | |
|---|---|---|---|---|
| baseToImgX-1.0.tar.gz | 2.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| baseToImgX-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 kB
Release files / baseToImgX-1.0.tar.gz
| Download URL | baseToImgX-1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b9de03bb9c9471ace30def7387b1298b86b4ed04de40996129fb53af417badf
|
|
BLAKE2b-256 checksum How to use checksums |
97034aec0b9a65a6bfb32ff000aad47cc5b8d9ff5305a6a55af243bf9d143ce0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.0
|
Release files / baseToImgX-1.0-py3-none-any.whl
| Download URL | baseToImgX-1.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05ed47e8afc48378573f240bb754d7468c39943641c8e0cd9f849083376ae8e3
|
|
BLAKE2b-256 checksum How to use checksums |
87b7d4a30da6bfeba6ee95ef8612b2fc5d4cc5d81f1a4af5f294b2d421154362
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.0
|
Security for baseToImgX 1.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.
