1 maintainer
Metadata
1 maintainer
Release files for asfenix-cpu 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 | |
|---|---|---|---|---|
| asfenix_cpu-0.1.0.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asfenix_cpu-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.5 kB
Release files / asfenix_cpu-0.1.0.tar.gz
| Download URL | asfenix_cpu-0.1.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4533b1a5480863fb82dba8b6ae7b7b715d37dbad3e694415e2d990ced22d150b
|
|
BLAKE2b-256 checksum How to use checksums |
4bbb00d7885a7d32a793c2557ad691ea2ec604d39b6e80c78a4af649092af174
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / asfenix_cpu-0.1.0-py3-none-any.whl
| Download URL | asfenix_cpu-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e98f634c714cef6d693b1ca5c931228930323f1448bb01a5d7963004f929573a
|
|
BLAKE2b-256 checksum How to use checksums |
523db17cda71b4590cc00624550f1f030f978b754bbc45c8ffd91c53c6d6d47d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for asfenix-cpu 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.
