The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for appdriver 0.1.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 | |
|---|---|---|---|---|
| appdriver-0.1.0.tar.gz | 48.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| appdriver-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 113.6 kB
Release files / appdriver-0.1.0.tar.gz
| Download URL | appdriver-0.1.0.tar.gz |
|---|---|
| Size | 48.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54b419a6090dc2d17c3a634e5967bbe74891b759e764820781c8de7575824e4d
|
|
BLAKE2b-256 checksum How to use checksums |
fe7beee8f80ab75317c2a0c805eaa29a3caf630f0dd7090633b14b877dbf75e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / appdriver-0.1.0-py3-none-any.whl
| Download URL | appdriver-0.1.0-py3-none-any.whl |
|---|---|
| Size | 65.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
325e5d8a3d2f1c62ebf6ec870c2afc52cc46b10b594745896bbef02e4b024806
|
|
BLAKE2b-256 checksum How to use checksums |
876075dd32f5c1e83a41fd4f8c6ac4f62642816fa16760f13a1943163d09d4b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for appdriver 0.1.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.
