The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for futurapay 0.3.4
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 | |
|---|---|---|---|---|
| futurapay-0.3.4.tar.gz | 2.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| futurapay-0.3.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / futurapay-0.3.4.tar.gz
| Download URL | futurapay-0.3.4.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe2aaf7d8481d9ea3a71675e4b0ab44158f005942dcc20c8d22a4bbe60f71bf1
|
|
BLAKE2b-256 checksum How to use checksums |
c8a982fc4db7c2401ec510ad3cf0f53dd06be9eb717deb714d428efea7e06f41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.12
|
Release files / futurapay-0.3.4-py3-none-any.whl
| Download URL | futurapay-0.3.4-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ccea18844a22f88b0aa46e866fe549da4b1ff8891ddb81de209aadc6898cc4e
|
|
BLAKE2b-256 checksum How to use checksums |
247f4a0c1950891430abcc48d29fa11e5e07cd66c753449bfeb82278b5eaab6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.12
|
Security for futurapay 0.3.4
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.
