The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for asilbek 0.1.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 | |
|---|---|---|---|---|
| asilbek-0.1.1.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asilbek-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 kB
Release files / asilbek-0.1.1.tar.gz
| Download URL | asilbek-0.1.1.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f48180ae328bdc251975c4a1b5ee1f076185fba2dcf5e04910ae148048ac7277
|
|
BLAKE2b-256 checksum How to use checksums |
0e1f618956a55019b7a3835a8916bae120f05b8c0f5b3ad79c5ff7160feaa4bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / asilbek-0.1.1-py3-none-any.whl
| Download URL | asilbek-0.1.1-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba48104a5e771fa875eae8c13d05aefa6ce9faf5937cc4cb46fcf9b656c4b097
|
|
BLAKE2b-256 checksum How to use checksums |
56081338944059dd1465505491b387f0d5effe00ad44c889581ceec62be14357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for asilbek 0.1.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.
