The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for forker 0.1.3
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 | |
|---|---|---|---|---|
| forker-0.1.3.tar.gz | 21.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| forker-0.1.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 43.2 kB
Release files / forker-0.1.3.tar.gz
| Download URL | forker-0.1.3.tar.gz |
|---|---|
| Size | 21.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
588adc48bd7303bcce9468f0d4112d366f16bbcbdb271e040f359ae9d42fb80f
|
|
BLAKE2b-256 checksum How to use checksums |
270ec364ed6749b067863d6cc9faf1701608d19cd377a0c8caa364ca861148b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Release files / forker-0.1.3-py2.py3-none-any.whl
| Download URL | forker-0.1.3-py2.py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
71511d89c6f19a48e58c491c99d280d6b15f8392f2a7f08ae3a060df1ced451c
|
|
BLAKE2b-256 checksum How to use checksums |
46cf5530366244d9f0bac39917fc1a7d305acaffe4539c76098d230a3cd95629
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Security for forker 0.1.3
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.
