Metadata
1 maintainer
Release files for opentelemetry-sdk 1.45.1
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 | |
|---|---|---|---|---|
| opentelemetry_sdk-1.45.1.tar.gz | 218.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opentelemetry_sdk-1.45.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 358.4 kB
Release files / opentelemetry_sdk-1.45.1.tar.gz
| Download URL | opentelemetry_sdk-1.45.1.tar.gz |
|---|---|
| Size | 218.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63d24a6ca645019a631e6a51999c73e93adcac1196ca640b8ae78a7cc4762bf3
|
|
BLAKE2b-256 checksum How to use checksums |
a1797392e21a1c8f0c61d90b223e31c7e48cb9d452e91a6b820ad24cca5f23c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Release files / opentelemetry_sdk-1.45.1-py3-none-any.whl
| Download URL | opentelemetry_sdk-1.45.1-py3-none-any.whl |
|---|---|
| Size | 140.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c604c11dc429810812348989115fa44bd558772a3d7442afc43d024f2c250ca4
|
|
BLAKE2b-256 checksum How to use checksums |
953c87c42b4bd6dd297536f04cd9383d212ac557ecd49f2cbdcd46da1c9ef5c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Security for opentelemetry-sdk 1.45.1
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.
