Case file No.234 · pypi · stdio

MemoryGuard

io.github.MerakOsiris/memoryguard · v0.7.15

Local-first governed MCP memory backend for coding agents.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 24 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

188 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v0.7.15)Oct 17, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is MemoryGuard safe?

MCPWatch gives MemoryGuard a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does MemoryGuard have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package agent-memguard. That is not proof of safety.

When was MemoryGuard last updated?

The latest registry version is 0.7.15, published Sep 30, 2026. The last push to MerakOsiris/memoryguard was on Sep 30, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does MemoryGuard use?

GitHub reports the license of MerakOsiris/memoryguard as MIT.

Related servers

same publisher / similar score