1 maintainer
Metadata
1 maintainer
Release files for rambler-google-activator 0.1.2
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 | |
|---|---|---|---|---|
| rambler_google_activator-0.1.2.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rambler_google_activator-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.3 kB
Release files / rambler_google_activator-0.1.2.tar.gz
| Download URL | rambler_google_activator-0.1.2.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fc06522708d13a90b389ed29ffe17ee055c707420cb593722356e61c4b5d937
|
|
BLAKE2b-256 checksum How to use checksums |
46f71c1d8991d9d3692fe8efea10108c2a61c7dedcc1d284b1dae700328d28f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.1
|
Release files / rambler_google_activator-0.1.2-py3-none-any.whl
| Download URL | rambler_google_activator-0.1.2-py3-none-any.whl |
|---|---|
| Size | 2.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1f0f28ec5f9d81ee4d27a20526d6ee387b0a64e2de60178a6a62979b39a7816
|
|
BLAKE2b-256 checksum How to use checksums |
f9ad7e3c2c00268f1f06ad17e966b403bdcc7252bd5f0b292790272e3290da1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.1
|
Security for rambler-google-activator 0.1.2
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.
