A previous release had provenance metadata, but this release does not. View details.
agora-mnemo is now inspeximus
pip uninstall agora-mnemo && pip install inspeximus
from inspeximus import Inspeximus
This release contains no implementation. It depends on inspeximus and re-exports it, so existing
imports and the mnemo / mnemo-mcp commands keep working while emitting a deprecation warning.
The last release carrying its own code was 1.24.4. Everything since — proof-of-deletion certificates,
per-tenant isolation, tamper-evident receipts, bitemporal queries, influence gating, ten framework
adapters — is in inspeximus.
Metadata
Release files for agora-mnemo 1.25.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agora_mnemo-1.25.0-py3-none-any.whl | Python 3 | none | any | Details for agora_mnemo-1.25.0-py3-none-any.whl |
Release files / agora_mnemo-1.25.0-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | agora_mnemo-1.25.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
735260bd40f5b839fef8b6fefe9e112b8735558a44e4ce35ba9c1081a5222bff
|
|
BLAKE2b-256 checksum How to use checksums |
d8449b29c1a32611be29578ed9f409d8eb1d0ae80129acb5d9956df7bd3f21ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.10
|
Security for agora-mnemo 1.25.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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 1.24.4 2 files With provenance
- Added 1.25.0 1 file Without provenance
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.