The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for azureconnquery 0.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 | |
|---|---|---|---|---|
| azureconnquery-0.1.tar.gz | 806 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| azureconnquery-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.9 kB
Release files / azureconnquery-0.1.tar.gz
| Download URL | azureconnquery-0.1.tar.gz |
|---|---|
| Size | 806 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
faa1dc50f0bdffbf8b674208ac6fa4561d582223caf7042eca188789fdaa9172
|
|
BLAKE2b-256 checksum How to use checksums |
9dea147015d3f5979ad4ff30c5522a8dd341b64b7414bef776ef67882c1455a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / azureconnquery-0.1-py3-none-any.whl
| Download URL | azureconnquery-0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
280deb24723e3e92ecfe4b09ed4a5588d5c5f996f8106a5c9dc332a92236cb6e
|
|
BLAKE2b-256 checksum How to use checksums |
6179723a399471a8b32721c5cf0dee915d2e52cf17945be2e746e06cd3fc8f23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for azureconnquery 0.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.
