The author of this package has not provided a project description
Metadata
Release files for ascellastacelonas 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 | |
|---|---|---|---|---|
| ascellastacelonas-0.1.0.tar.gz | 3.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ascellastacelonas-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 kB
Release files / ascellastacelonas-0.1.0.tar.gz
| Download URL | ascellastacelonas-0.1.0.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dfada35f031e7a90f38849920e66dd12cbfc3c42aea3af00ed53d56eaa1ffe0
|
|
BLAKE2b-256 checksum How to use checksums |
cda2a0b43c53c918209772235d4a47c8e0e028abebf70e0786370e3a2ce6d778
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Release files / ascellastacelonas-0.1.0-py3-none-any.whl
| Download URL | ascellastacelonas-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2cfc54212e9ce19fad419b8f7a49bd345333d12582f54f82c1d1bde6987c83b
|
|
BLAKE2b-256 checksum How to use checksums |
26558651b4600060fc1201dbc7ad006d2c191ecea464973b9a24cc574e33fbea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Security for ascellastacelonas 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.