1 maintainer
Metadata
1 maintainer
Release files for memoryengineering 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 | |
|---|---|---|---|---|
| memoryengineering-0.0.1.tar.gz | 1.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| memoryengineering-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 kB
Release files / memoryengineering-0.0.1.tar.gz
| Download URL | memoryengineering-0.0.1.tar.gz |
|---|---|
| Size | 1.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2837f26379af1fffc0584068f7fc8de20d6994bdfef91f644a68ddc05683109d
|
|
BLAKE2b-256 checksum How to use checksums |
80599903838a9de49700821a47d813325a668aac25d72937dc31fc369868d614
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / memoryengineering-0.0.1-py3-none-any.whl
| Download URL | memoryengineering-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
461846b0a3b00b3c4bdf5b0e96bed9bb3fad301d358d8871b19f2873956f9a75
|
|
BLAKE2b-256 checksum How to use checksums |
460a17259aa176c8afdd5218440dd41afa3af25f313b8a24dfee7488d20fdbf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for memoryengineering 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.
