The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for augury-vx 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 | |
|---|---|---|---|---|
| augury_vx-0.0.1.tar.gz | 394 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| augury_vx-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / augury_vx-0.0.1.tar.gz
| Download URL | augury_vx-0.0.1.tar.gz |
|---|---|
| Size | 394 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
319f091593a044179034b211947441301708636894e55296a8b2dcd9b35c1d1a
|
|
BLAKE2b-256 checksum How to use checksums |
eb96f38989e3a451f3d35d7debb25630926b3d3733eda5debe03e43de1f65b93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / augury_vx-0.0.1-py3-none-any.whl
| Download URL | augury_vx-0.0.1-py3-none-any.whl |
|---|---|
| Size | 984 Bytes |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f50cf32d25c2762caae7ceea773c66e0fa0de1f314869a2ae7a1cdca2555add
|
|
BLAKE2b-256 checksum How to use checksums |
b2399d893cca048da5d2729f3dd947968c852a758b1d91369a68f260e82fff5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for augury-vx 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.
