1 maintainer
Metadata
1 maintainer
Release files for arcmemory-bendex 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 | |
|---|---|---|---|---|
| arcmemory_bendex-0.1.0.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arcmemory_bendex-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.4 kB
Release files / arcmemory_bendex-0.1.0.tar.gz
| Download URL | arcmemory_bendex-0.1.0.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0bcdbca26f228a26e5cd550df7c4d1eb30ffde820d71eb944ce6c2d925bd8208
|
|
BLAKE2b-256 checksum How to use checksums |
cbf3bd25f9be89fdf692797f6ab003f4842334976fab7b15e948e6f86d8fff48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Release files / arcmemory_bendex-0.1.0-py3-none-any.whl
| Download URL | arcmemory_bendex-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81e2d7385d8a4d553d2ceba83d4cc657dc6aa4dfc2f6899ae1b9a26958974646
|
|
BLAKE2b-256 checksum How to use checksums |
b66ccb39eef189661a81a502f0b693b7686a2c237c1567ae0c5bb619830c5ca0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.13
|
Security for arcmemory-bendex 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.
