The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for basalunit 1.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 | |
|---|---|---|---|---|
| basalunit-1.1.0.tar.gz | 21.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| basalunit-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.6 kB
Release files / basalunit-1.1.0.tar.gz
| Download URL | basalunit-1.1.0.tar.gz |
|---|---|
| Size | 21.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f45b16fd16e2af3a5e716ce14f84dd4b25c35f4d27d30aff2f25e7a6487dd93b
|
|
BLAKE2b-256 checksum How to use checksums |
6c945e21b33de46425322227dd493c54f9def96ee06f260d95ff44904577716d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Release files / basalunit-1.1.0-py3-none-any.whl
| Download URL | basalunit-1.1.0-py3-none-any.whl |
|---|---|
| Size | 32.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ef4527aed326da2828e7d8ffd699516fef1da92fffc4f0093b208dafe1374de
|
|
BLAKE2b-256 checksum How to use checksums |
3b07eff8a9ead184447eba3d37d5c107f6111b6d1b5a985f5ac03f104b56aa19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for basalunit 1.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.
