Release files for git-remote-hg 1.0.5
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 | |
|---|---|---|---|---|
| git_remote_hg-1.0.5.tar.gz | 38.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_remote_hg-1.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 78.5 kB
Release files / git_remote_hg-1.0.5.tar.gz
| Download URL | git_remote_hg-1.0.5.tar.gz |
|---|---|
| Size | 38.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2aedfd3762efcef001359cec230ecc592236c37024530d85befe2771e79b56fa
|
|
BLAKE2b-256 checksum How to use checksums |
800f447b9002ed469cbdd5e58ba65730f2ec328502265791ba9c09cb7b6e45e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / git_remote_hg-1.0.5-py3-none-any.whl
| Download URL | git_remote_hg-1.0.5-py3-none-any.whl |
|---|---|
| Size | 39.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d84be32a5bbeb5e587b463d60ba35431c35ebbde85051b193f055fcab8c69adc
|
|
BLAKE2b-256 checksum How to use checksums |
513557255c0562e60c4083075a6ed05e0e64abff78e24eee206353e0145ee85d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for git-remote-hg 1.0.5
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.
