The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for smtp2goapi 1.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 | |
|---|---|---|---|---|
| smtp2goapi-1.0.0.tar.gz | 4.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| smtp2goapi-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.4 kB
Release files / smtp2goapi-1.0.0.tar.gz
| Download URL | smtp2goapi-1.0.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de188fcad66ca84189fb6e77abca544791120e931097e093952b37586fe4a8fe
|
|
BLAKE2b-256 checksum How to use checksums |
c8323f80bd1406eaddb760a0f2269baf96dd70d2cc3a6e186a02976b3a1799c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.4
|
Release files / smtp2goapi-1.0.0-py3-none-any.whl
| Download URL | smtp2goapi-1.0.0-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b17b06de681e1cbf923348bc1cd404b1c2bb8ccbbdd5b6265fa8f75ec76d610e
|
|
BLAKE2b-256 checksum How to use checksums |
9590a017e827b1b9853fac30ec9d007cfe76dc8732e5ee86fe7a8c566d386ea6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.4
|
Security for smtp2goapi 1.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.
