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