UNKNOWN
1 maintainer
Metadata
1 maintainer
Release files for Anvil-Uplink-Windows-Service 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 | |
|---|---|---|---|---|
| Anvil_Uplink_Windows_Service-0.0.1.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Anvil_Uplink_Windows_Service-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.8 kB
Release files / Anvil_Uplink_Windows_Service-0.0.1.tar.gz
| Download URL | Anvil_Uplink_Windows_Service-0.0.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
34082eb132408656fcec678b3f9ab9c06c8aa3f77fadcc90a9592117d766d62b
|
|
BLAKE2b-256 checksum How to use checksums |
83af971f7f36cdc7e66f41246fa980ba67af8cd143a0fcc0c138ac01eb81acd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / Anvil_Uplink_Windows_Service-0.0.1-py3-none-any.whl
| Download URL | Anvil_Uplink_Windows_Service-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01d46242b589a1b595b05e3694ab910230456f986f3741da55e3a8a1d75b3bcd
|
|
BLAKE2b-256 checksum How to use checksums |
73eb39fcc4fdd28bb0c48a4b79b57c0f323ee2da137ee28f97554db3e102e871
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Anvil-Uplink-Windows-Service 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.
