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