The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for git-limiter 0.1.1
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_limiter-0.1.1.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| git_limiter-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.1 kB
Release files / git_limiter-0.1.1.tar.gz
| Download URL | git_limiter-0.1.1.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
90b76f84313990fb70c342d4e46681315955acfd6c08fbf72df87a8c6ac3c3a9
|
|
BLAKE2b-256 checksum How to use checksums |
fa9b7e76e9dee9edb5a1e81b8ce1e38de75d13319e26d0a1517f35f76afc4a67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.11.2 Darwin/22.3.0
|
Release files / git_limiter-0.1.1-py3-none-any.whl
| Download URL | git_limiter-0.1.1-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aefbf633860f9387397383d63a327c50dd537c5f1e265640d65a071d72ef245f
|
|
BLAKE2b-256 checksum How to use checksums |
b18f098241dccf66fc8cf4f3448c02cb79e7a4942f285724b429250efa22293e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.11.2 Darwin/22.3.0
|
Security for git-limiter 0.1.1
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.
