Metadata
Release files for backup-tracker-micro 0.1.9
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 | |
|---|---|---|---|---|
| backup_tracker_micro-0.1.9.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| backup_tracker_micro-0.1.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.5 kB
Release files / backup_tracker_micro-0.1.9.tar.gz
| Download URL | backup_tracker_micro-0.1.9.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14b5501dbf7b09adabcefdfe99d601c9bd17b1c54c216063f6b8fe67e36f9a98
|
|
BLAKE2b-256 checksum How to use checksums |
ab53283d3223f4ebbb415dcfa0c2ae5833c1ff0710ea6853302bf32e83c8cf34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Release files / backup_tracker_micro-0.1.9-py3-none-any.whl
| Download URL | backup_tracker_micro-0.1.9-py3-none-any.whl |
|---|---|
| Size | 3.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a80e2cbcd172ee489876df24caf64a4b93c0c707ec1ae3609f7b14aa0db53336
|
|
BLAKE2b-256 checksum How to use checksums |
ef08ff3abdb20742df52b0aca433a9dd479b7fd8c9dfe1bf08445178fe57f78b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Security for backup-tracker-micro 0.1.9
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.