The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for zeitgeber 0.0.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 | |
|---|---|---|---|---|
| zeitgeber-0.0.2.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zeitgeber-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 kB
Release files / zeitgeber-0.0.2.tar.gz
| Download URL | zeitgeber-0.0.2.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42772d2e4e4c6c73b8799c7efdf71e9758de63a5766b0f47aeefb69fb92561b0
|
|
BLAKE2b-256 checksum How to use checksums |
a9fd643c6a2505f857c22f8a575b6242905aa79d5f9e5cfdcd7d75064478db3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.11
|
Release files / zeitgeber-0.0.2-py3-none-any.whl
| Download URL | zeitgeber-0.0.2-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed34730d24ae2f72f592044f67303dfb24ba1e0532b3470a3caf3f202d903853
|
|
BLAKE2b-256 checksum How to use checksums |
4f1c6d30bd05a666fbd739c67bb9dc35ba2b500e8377053214f0c576dbf3ea20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.11
|
Security for zeitgeber 0.0.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.
