Metadata
Release files for basic-rust-fib-py 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 | |
|---|---|---|---|---|
| basic_rust_fib_py-0.1.0.tar.gz | 3.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| basic_rust_fib_py-0.1.0-cp38-none-win_amd64.whl | CPython 3.8 | none | Windows x86-64 | Details |
Total release size: 113.9 kB
Release files / basic_rust_fib_py-0.1.0.tar.gz
| Download URL | basic_rust_fib_py-0.1.0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f69b5617e2517ed6da4a172686daad83f003dcf1386bd7effad45b2763abe5c
|
|
BLAKE2b-256 checksum How to use checksums |
7e3d50817de6dd1ece73be7c6f5e1583df1844651131cd0822d83b6b1f09e688
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.3.0
|
Release files / basic_rust_fib_py-0.1.0-cp38-none-win_amd64.whl
| Download URL | basic_rust_fib_py-0.1.0-cp38-none-win_amd64.whl |
|---|---|
| Size | 110.4 kB |
| Tags | CPython 3.8 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c1ae2f00dc9e4bcfe2377da89672b1f24f6673fd976196751d45150ce3831f23
|
|
BLAKE2b-256 checksum How to use checksums |
695b9cebcb3dff90140e9b22a95d230e199d8825ea4c93497d8aeaf608f9c696
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
maturin/1.3.0
|
Security for basic-rust-fib-py 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.