The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for grive-walker 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 | |
|---|---|---|---|---|
| grive_walker-0.0.1.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| grive_walker-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.0 kB
Release files / grive_walker-0.0.1.tar.gz
| Download URL | grive_walker-0.0.1.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8cedc057ac5fb937b83f032a6127df57b0962e65616cc6c8d517831491f1ced2
|
|
BLAKE2b-256 checksum How to use checksums |
b91fe11893019dbf109697fa1210fb6ecb39183a5582f6c11ac7a2ecdbf80d25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Release files / grive_walker-0.0.1-py3-none-any.whl
| Download URL | grive_walker-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f477e106e18156cc4491effb54853550afd91c61cda19e7deff947e979afcb5
|
|
BLAKE2b-256 checksum How to use checksums |
935de1bf42372c1e1ac63b23aad958b54c42a02e7c292804a59b6f8342a2d150
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Security for grive-walker 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.
