The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for fisspy 1.4.5
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 | |
|---|---|---|---|---|
| fisspy-1.4.5.tar.gz | 140.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fisspy-1.4.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 291.6 kB
Release files / fisspy-1.4.5.tar.gz
| Download URL | fisspy-1.4.5.tar.gz |
|---|---|
| Size | 140.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ad454c7545d0d9b415eac46c71443ea49beb6ed1fd5075f76cd4a829d21dd92
|
|
BLAKE2b-256 checksum How to use checksums |
07f9c1ae43f7b96404d9287868a1a3d92a921f291bc79207dd55a4aefd158e78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.0
|
Release files / fisspy-1.4.5-py3-none-any.whl
| Download URL | fisspy-1.4.5-py3-none-any.whl |
|---|---|
| Size | 151.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3bf1d3cbda09b4ea4e55e35f2ceee91668c271e557e3a8826fd9a2a3ea987fa9
|
|
BLAKE2b-256 checksum How to use checksums |
fdc048a2a15a5cffe1240ba55279a1607cff3cb930362d7419df1b4308a5cd56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.0
|
Security for fisspy 1.4.5
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.
