The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for contactssync 0.1.28
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 | |
|---|---|---|---|---|
| contactssync-0.1.28.tar.gz | 32.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| contactssync-0.1.28-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 70.2 kB
Release files / contactssync-0.1.28.tar.gz
| Download URL | contactssync-0.1.28.tar.gz |
|---|---|
| Size | 32.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed1cd8085ff406984ebc88fa055989aa4a08eb45d937e36cad0fa39096d3081f
|
|
BLAKE2b-256 checksum How to use checksums |
1e78c74367b32b16f13e7d9d5927787057881cc05dc2763216845bdce43d7331
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Release files / contactssync-0.1.28-py3-none-any.whl
| Download URL | contactssync-0.1.28-py3-none-any.whl |
|---|---|
| Size | 37.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
acda62810ed063a468c5a6e0b97ae206812e61209b0412b6f35fa08605822862
|
|
BLAKE2b-256 checksum How to use checksums |
51a16d8223afb8633bde62c7548e4827f296597ac93020874602fd03eac60196
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.12
|
Security for contactssync 0.1.28
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.
