Metadata
Release files for promptflow-sdk-bundle 0.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 | |
|---|---|---|---|---|
| promptflow-sdk-bundle-0.0.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| promptflow_sdk_bundle-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.4 kB
Release files / promptflow-sdk-bundle-0.0.1.tar.gz
| Download URL | promptflow-sdk-bundle-0.0.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80f0823f6f9effa4b86eea6c39fe5ef2ff82cf3f7df1e2128a4bddbfe56c5735
|
|
BLAKE2b-256 checksum How to use checksums |
1a9efc0a51c257e132488192dda4fb4969583870adcf4280de0b188c78018a4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / promptflow_sdk_bundle-0.0.1-py3-none-any.whl
| Download URL | promptflow_sdk_bundle-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
000d9142c660db6fa04d6c7f0ddfd02edff18241838aa2d5bdec663748e1cfa8
|
|
BLAKE2b-256 checksum How to use checksums |
cd1c1d1fae953bb8be10d21cb061e2ad005cf582aeac66b83770ce91b2935605
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for promptflow-sdk-bundle 0.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.