1 maintainer
Metadata
1 maintainer
Release files for git-draft 0.53.2
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_draft-0.53.2.tar.gz | 29.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_draft-0.53.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 71.0 kB
Release files / git_draft-0.53.2.tar.gz
| Download URL | git_draft-0.53.2.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
206ac6684a287eda5ceb639a4239d8e0b7593d71184e5aa6c2ad3e1796015d03
|
|
BLAKE2b-256 checksum How to use checksums |
9a57a20ec8615d4322a1bfcfe09f567050d25bb42b17e2aa8c8ca2388ecb2bbf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.1 CPython/3.12.12 Linux/6.14.0-1017-azure
|
Release files / git_draft-0.53.2-py3-none-any.whl
| Download URL | git_draft-0.53.2-py3-none-any.whl |
|---|---|
| Size | 41.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
58e6c56e381d66a20b3042fec83fe8b6afc2207fef0118a0b856957f3848f881
|
|
BLAKE2b-256 checksum How to use checksums |
e4eff20c82062167bdda4fc520bd02ebc2f4dcf8ebf49261bacbdd334d94e279
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.1 CPython/3.12.12 Linux/6.14.0-1017-azure
|
Security for git-draft 0.53.2
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.
