1 maintainer
Metadata
1 maintainer
Release files for sagemaker-serve 1.26.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 | |
|---|---|---|---|---|
| sagemaker_serve-1.26.0.tar.gz | 245.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sagemaker_serve-1.26.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 548.8 kB
Release files / sagemaker_serve-1.26.0.tar.gz
| Download URL | sagemaker_serve-1.26.0.tar.gz |
|---|---|
| Size | 245.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4140f101420a21bf8826b02c10cc8f5fb4ee4e3adb44491e5dbfe9c42033303
|
|
BLAKE2b-256 checksum How to use checksums |
02e22fd9f3bf07b8c45cafa9d9bbec80544531838bbd81d4421927a67c006813
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / sagemaker_serve-1.26.0-py3-none-any.whl
| Download URL | sagemaker_serve-1.26.0-py3-none-any.whl |
|---|---|
| Size | 303.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6a4b8ddbd6692fe73f45f614c80cc02710adee19a2b80afc04e49f0d987e52fd
|
|
BLAKE2b-256 checksum How to use checksums |
447db739408085010461092a78ce0184ca8cb0f759aa8afa2edf37da31c88cf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for sagemaker-serve 1.26.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.
