axpsystems\nAlias for axp - https://axp.systems
1 maintainer
Metadata
1 maintainer
Release files for axpsystems 0.0.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 | |
|---|---|---|---|---|
| axpsystems-0.0.1.tar.gz | 609 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| axpsystems-0.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 1.7 kB
Release files / axpsystems-0.0.1.tar.gz
| Download URL | axpsystems-0.0.1.tar.gz |
|---|---|
| Size | 609 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea8c2a60c193f8bed6ecba796969ccdfdc95c0a60b172e01a8b07e76c67184c9
|
|
BLAKE2b-256 checksum How to use checksums |
1dd747428f3b7e174a778ca032e09413622e9785ba1c6e0b9cac624826987ebb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / axpsystems-0.0.1-py2.py3-none-any.whl
| Download URL | axpsystems-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
74d5df22225ca8b3a0a4261b648e65f7c6b1e438182c6f7d45619d94cc5e44c3
|
|
BLAKE2b-256 checksum How to use checksums |
8dbb2a43a5066ce730b1ee10544b10c2c2e51c8103f343e837a8816450818d83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for axpsystems 0.0.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.
