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