The author of this package has not provided a project description
Metadata
Release files for helperforpy 0.1.0
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 | |
|---|---|---|---|---|
| helperforpy-0.1.0.tar.gz | 794 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| helperforpy-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 kB
Release files / helperforpy-0.1.0.tar.gz
| Download URL | helperforpy-0.1.0.tar.gz |
|---|---|
| Size | 794 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4af29440a7d5df69c277772a72fa388d02eaeb0805e0a0ed42c8a29e9ecba4c
|
|
BLAKE2b-256 checksum How to use checksums |
798a85f0351d64788e686f1b5ac4f2186b1a6129c234dbb7987a9fb5348388ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Release files / helperforpy-0.1.0-py3-none-any.whl
| Download URL | helperforpy-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
367bdb877e7b17bfdb67fd4e125b8dc614c5aeb423e2c89f23150644de77fe84
|
|
BLAKE2b-256 checksum How to use checksums |
95845c1aa70044fda6941a94e03bfbbaa31560157269597b865d211bfd0795ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.13
|
Security for helperforpy 0.1.0
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.