The author of this package has not provided a project description
Metadata
Release files for csgoogleanalytics 2.13
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 | |
|---|---|---|---|---|
| csgoogleanalytics-2.13.tar.gz | 9.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| csgoogleanalytics-2.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.0 kB
Release files / csgoogleanalytics-2.13.tar.gz
| Download URL | csgoogleanalytics-2.13.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9160a847ace7dc51643943d31cc0ee1e37fbbd0b7bb99b2a9399d3d6764c9623
|
|
BLAKE2b-256 checksum How to use checksums |
f53a0b6c6768c042814ff5c34e523b4b192c25f6914b898a86edd03bf66cf9c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / csgoogleanalytics-2.13-py3-none-any.whl
| Download URL | csgoogleanalytics-2.13-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8829bda41654384efac437e020bdd191cdb6fb4708089e701c9e73dcaa565ade
|
|
BLAKE2b-256 checksum How to use checksums |
3b0490eef8330afd358dc5d2ba8a39eca055f21f258bd76d317695ba91d4ea8e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for csgoogleanalytics 2.13
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.