The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for ftransfer 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 | |
|---|---|---|---|---|
| ftransfer-0.1.0.tar.gz | 2.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftransfer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / ftransfer-0.1.0.tar.gz
| Download URL | ftransfer-0.1.0.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
74d849831d6727e11d1aca276090daa3c1b62ac2785779cd257cd614e6c63ff6
|
|
BLAKE2b-256 checksum How to use checksums |
f9856ccda239e208b93bfd94a9e23401495f23a0c3dbc82fdc3ad46dc70ae043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.5
|
Release files / ftransfer-0.1.0-py3-none-any.whl
| Download URL | ftransfer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94d07041b36debe2d869c45432d416b9944b34592a2e5b74cfca2984b6cb728c
|
|
BLAKE2b-256 checksum How to use checksums |
d693e2241b9951879b90253f15bf21e4d23bce748ae5c73e36125391e19cebec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.5
|
Security for ftransfer 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.
