1 maintainer
Metadata
1 maintainer
Release files for sagemaker-serve 1.27.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.27.0.tar.gz | 247.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sagemaker_serve-1.27.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 551.7 kB
Release files / sagemaker_serve-1.27.0.tar.gz
| Download URL | sagemaker_serve-1.27.0.tar.gz |
|---|---|
| Size | 247.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1275ba46158c8419a3ede7be0d8657ace69b2ed86c6dcd377860bbafc585805e
|
|
BLAKE2b-256 checksum How to use checksums |
49e8e0e8514df53d182e6f7cd148ed7588acecdd3b5dcdbca4c60ae8bba1d96e
|
| 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.27.0-py3-none-any.whl
| Download URL | sagemaker_serve-1.27.0-py3-none-any.whl |
|---|---|
| Size | 304.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fd66dca9b103e18ddfe7a58ce121eeac25e8530cd71a11cbabb24539085f0ce5
|
|
BLAKE2b-256 checksum How to use checksums |
dbcba320150a59277e6a0070029953c19b1452384af06d3864b6d9f760388173
|
| 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.27.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.
