A native Python SDK for the Trolley API
2 maintainers
Metadata
2 maintainers
Release files for paymentrails 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 | |
|---|---|---|---|---|
| paymentrails-0.2.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| paymentrails-0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.9 kB
Release files / paymentrails-0.2.tar.gz
| Download URL | paymentrails-0.2.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
018da283648945f7dfa66ce5d606ae41712fa408977d697a0464cb11442eba89
|
|
BLAKE2b-256 checksum How to use checksums |
f2d86c5c69f5e6f0a39f69d47e9c121b25a869969c15934b6caf0ff27f887906
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Release files / paymentrails-0.2-py3-none-any.whl
| Download URL | paymentrails-0.2-py3-none-any.whl |
|---|---|
| Size | 18.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
454966eede4a23346b5276c13ac2f9d70621eb938c7f699d2b0e2a1b5213d1a3
|
|
BLAKE2b-256 checksum How to use checksums |
0b7388d71145e3058856a8d93e01649ac56d34b9ed090dd8f225c6dc747fe90d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Security for paymentrails 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.
