The author of this package has not provided a project description
Metadata
Release files for py-Asterisk 0.6.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 | |
|---|---|---|---|---|
| py_asterisk-0.6.0.tar.gz | 20.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| py_asterisk-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.2 kB
Release files / py_asterisk-0.6.0.tar.gz
| Download URL | py_asterisk-0.6.0.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f72caef0c556be53cddcbbf31fb6ac8ebe3b58acd481d245f0e4e5d7a58ccdd
|
|
BLAKE2b-256 checksum How to use checksums |
0a58ce09765c0373df4cac204e08a50ed29505d3080339f82b3a7af7f13a7e9d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Release files / py_asterisk-0.6.0-py3-none-any.whl
| Download URL | py_asterisk-0.6.0-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
92a35a65889c63e5dc93f5815b9ed047bdefb0061c0780a626b0e2deb4c22ed7
|
|
BLAKE2b-256 checksum How to use checksums |
d8a56ecd58d46c97c0f1e2840d76a3e3c44c988abd864332eb9631768332bb4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Security for py-Asterisk 0.6.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.