The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for AzuriteSDK 1.0.2
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 | |
|---|---|---|---|---|
| azuritesdk-1.0.2.tar.gz | 3.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| azuritesdk-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.3 kB
Release files / azuritesdk-1.0.2.tar.gz
| Download URL | azuritesdk-1.0.2.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d5f98cd7e6c0cf786f3eac785ccbdf374b4456d31825c1c80b67ee2e2a2ceb4
|
|
BLAKE2b-256 checksum How to use checksums |
c0ba2e813975499ad79ac67c09bc30fce33557036fbd8280272b082b2b30266b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / azuritesdk-1.0.2-py3-none-any.whl
| Download URL | azuritesdk-1.0.2-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee60bf322f4733b91ce657f2f1af43511f4c565c7c686e5c67218fb824a10291
|
|
BLAKE2b-256 checksum How to use checksums |
c8d391d7c0d02263508d2d8cf85294b13144f4bec3151e963aca50c485d2c772
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for AzuriteSDK 1.0.2
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.
