1 maintainer
Metadata
1 maintainer
Release files for synth-sdk 0.3.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 | |
|---|---|---|---|---|
| synth_sdk-0.3.0.tar.gz | 38.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| synth_sdk-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 85.4 kB
Release files / synth_sdk-0.3.0.tar.gz
| Download URL | synth_sdk-0.3.0.tar.gz |
|---|---|
| Size | 38.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10cfaa36da6b8d101dfa1dfc19b0ac8bd5b4529eaa64fe81c09143d1fbeecc00
|
|
BLAKE2b-256 checksum How to use checksums |
0b5c33dc07bd1910d6ad4e5219a4b6fdda9819f2048fb119c093dda4b3d650d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Release files / synth_sdk-0.3.0-py3-none-any.whl
| Download URL | synth_sdk-0.3.0-py3-none-any.whl |
|---|---|
| Size | 46.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34a5a2b257fcfd35992a401434f6edc559a81c8634e0f16b322eea1417a37e38
|
|
BLAKE2b-256 checksum How to use checksums |
cd3da9dcd3cdbf14f1b644e6f7ec273fceb24e89ba3fe46d9e3cc99a2d4255fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Security for synth-sdk 0.3.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.
