1 maintainer
Metadata
1 maintainer
Release files for trlocal-backup 0.1.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 | |
|---|---|---|---|---|
| trlocal-backup-0.1.0.tar.gz | 3.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trlocal_backup-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.3 kB
Release files / trlocal-backup-0.1.0.tar.gz
| Download URL | trlocal-backup-0.1.0.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23bc67858bd7f6a91c1770ca24a69931ae510230ea8b44dbb19d47e22cd2f072
|
|
BLAKE2b-256 checksum How to use checksums |
e94a4b33ec56c8e2d5d709b33a3a53e9670630d8d6c032cfb72ed7e2ba6c6ee0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.3 Windows/10
|
Release files / trlocal_backup-0.1.0-py3-none-any.whl
| Download URL | trlocal_backup-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
033dad22d15ae1e4c4bc3bc72778797c495cd86ecc61200fd484421da2b4a569
|
|
BLAKE2b-256 checksum How to use checksums |
2bcbab76701284877a5659aff70930e75119b2ed7017287e0bb9211b4611bad4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.10 CPython/3.8.3 Windows/10
|
Security for trlocal-backup 0.1.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.
