The author of this package has not provided a project description
4 maintainers
Metadata
4 maintainers
Release files for twitter-ads 11.0.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 | |
|---|---|---|---|---|
| twitter-ads-11.0.0.tar.gz | 24.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| twitter_ads-11.0.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 51.2 kB
Release files / twitter-ads-11.0.0.tar.gz
| Download URL | twitter-ads-11.0.0.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6bbff93dbcd3f8901643513031243d12d237a187e5d177ca05616721cce9be4b
|
|
BLAKE2b-256 checksum How to use checksums |
7ecf232199a73c3fd7f4cfeb29adb7e9a1cb918f035421cdd33e6a393f3b0769
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Release files / twitter_ads-11.0.0-py2.py3-none-any.whl
| Download URL | twitter_ads-11.0.0-py2.py3-none-any.whl |
|---|---|
| Size | 26.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
da1e34854ee662a08c8b7e350ace8e9ac79ff1d2c364f641c221f583e02d8aa6
|
|
BLAKE2b-256 checksum How to use checksums |
ccfb11252e41fc02fddd36b836801797aec7296e4c3fcd962ac99509be642925
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for twitter-ads 11.0.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.
