The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for fysh-barracuda 0.0.1
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 | |
|---|---|---|---|---|
| fysh-barracuda-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fysh_barracuda-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 kB
Release files / fysh-barracuda-0.0.1.tar.gz
| Download URL | fysh-barracuda-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1796d7c8b2a7f8edb0d78bfcb42e766a8fc4f9863e032c0f18768811163f7b5
|
|
BLAKE2b-256 checksum How to use checksums |
89a78ce4cbdad2852284c37602121fab2c03b6f31bf6c279cf0953dff1326b4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.13
|
Release files / fysh_barracuda-0.0.1-py3-none-any.whl
| Download URL | fysh_barracuda-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0511fadedacc67e04817789c7a5fdd0da272deb5f7abb84f8b3d4ccb84278a1f
|
|
BLAKE2b-256 checksum How to use checksums |
860dd9ed579bb42d42a88d2a044505519ed16e9bb9b901a19cab6ad51c4cd43f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.9.13
|
Security for fysh-barracuda 0.0.1
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.
