Metadata
Release files for 3d-converter 0.9.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 | |
|---|---|---|---|---|
| 3d-converter-0.9.0.tar.gz | 40.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| 3d_converter-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.7 kB
Release files / 3d-converter-0.9.0.tar.gz
| Download URL | 3d-converter-0.9.0.tar.gz |
|---|---|
| Size | 40.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40da7029f58cf3af7a83047a132d61c810896a2039960b264ab28bae98d5981a
|
|
BLAKE2b-256 checksum How to use checksums |
ce41a9a21c001d2238fe671435c315ab8d22c243e3de3715eaf1bdcd3b95bd79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.3
|
Release files / 3d_converter-0.9.0-py3-none-any.whl
| Download URL | 3d_converter-0.9.0-py3-none-any.whl |
|---|---|
| Size | 55.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b03b9966294d2f74b81f1a114eed6ae0af5810f86d1b0cc5c5cb1b6c9fd9409
|
|
BLAKE2b-256 checksum How to use checksums |
7b02d9addde574336098c24d730f5a19d08bda700c9f6415a64deab5c73707d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.3
|
Security for 3d-converter 0.9.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.