inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail
io.github.DanceNitra/inspeximus · v3.21.0
Self-correcting agent memory: recall, supersede, revert, forget, GDPR erasure, audit receipts.
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devMetadata change timeline
rug-pull detection- v3.20.0 → v3.21.0Oct 20, 2026
versionchanged version bump"3.20.0" → "3.21.0"
packages.0.versionchanged package version bump"3.20.0" → "3.21.0"
- v3.19.1 → v3.20.0Oct 16, 2026
versionchanged version bump"3.19.1" → "3.20.0"
packages.0.versionchanged package version bump"3.19.1" → "3.20.0"
- First snapshot (v3.19.1)Oct 16, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail safe?
MCPWatch gives inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail a heuristic security score of 96/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package inspeximus. That is not proof of safety.
When was inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail last updated?
The latest registry version is 3.21.0, published Oct 19, 2026. The last push to DanceNitra/inspeximus was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.
What license does inspeximus: agent memory with provenance, GDPR erasure and a tamper-evident audit trail use?
GitHub reports the license of DanceNitra/inspeximus as MIT.