The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for backend00300 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 | |
|---|---|---|---|---|
| backend00300-0.1.0.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| backend00300-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.3 kB
Release files / backend00300-0.1.0.tar.gz
| Download URL | backend00300-0.1.0.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46d0057e84a510156db354b5dcff535e2bff392cdbe9b9bb5e85802496aed347
|
|
BLAKE2b-256 checksum How to use checksums |
8d9233dd0846c5b45fcff5ab2de49a83bd7846dba4c50d7150243a7a425271b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / backend00300-0.1.0-py3-none-any.whl
| Download URL | backend00300-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4dab3952c7deff7064bdae9e8146fdda8415c138d5c779b4409e93ea72d9743
|
|
BLAKE2b-256 checksum How to use checksums |
eeef8fde5547d41f1260074edac45627637f9a913ff62ef6e5c1f74acf2afaf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for backend00300 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.
