A collection of tools to work with go-to-market data
Metadata
Release files for gtmarket 0.1.7
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 | |
|---|---|---|---|---|
| gtmarket-0.1.7.tar.gz | 24.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gtmarket-0.1.7-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 52.2 kB
Release files / gtmarket-0.1.7.tar.gz
| Download URL | gtmarket-0.1.7.tar.gz |
|---|---|
| Size | 24.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95e0deda557488acef3909077c879c58a15a6893e9886e7e750d8e1d3e8d1567
|
|
BLAKE2b-256 checksum How to use checksums |
7fa06d0fb8799e73fde7d3f56f4a0bb58ae25f1e0d4243ef26d5472337911d54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Release files / gtmarket-0.1.7-py2.py3-none-any.whl
| Download URL | gtmarket-0.1.7-py2.py3-none-any.whl |
|---|---|
| Size | 27.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
1c0ef862052530a41d99908492f8d10d7ca9215e4199ebd5d2e07548dcc591b2
|
|
BLAKE2b-256 checksum How to use checksums |
f822305d4e4836dd9d8c651fbfe70a42fee0fbd922eae65e2be25688fb741b8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Security for gtmarket 0.1.7
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.