1 maintainer
Metadata
1 maintainer
Release files for oryks-google-drive 0.1.5
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 | |
|---|---|---|---|---|
| oryks_google_drive-0.1.5.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oryks_google_drive-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.0 kB
Release files / oryks_google_drive-0.1.5.tar.gz
| Download URL | oryks_google_drive-0.1.5.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea36a5020d255df6a6e0d9d7d08045c154536e3769dfe8132e3a3a6a214c6209
|
|
BLAKE2b-256 checksum How to use checksums |
a4ad9f92cc71bf38d3a55be14d35952346dd8701799040a859f33020d1af6b62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / oryks_google_drive-0.1.5-py3-none-any.whl
| Download URL | oryks_google_drive-0.1.5-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b161430bd26b184ac206c8e30ac494aabfedabe247a9969f3933bf14288e1bd
|
|
BLAKE2b-256 checksum How to use checksums |
3a6081599f3e2f27e5702bc6c41bbd9cca74893302821737efc2c6fef4c3c86a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for oryks-google-drive 0.1.5
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.
