Case file No.325 · pypi · stdio

Engram

io.github.TushaeBXN/engram · v1.10.5

Local, private long-term memory for AI: verbatim, searchable, correctable. No LLM or API key.

Package ↗GitHub ↗

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 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

390 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 (v1.10.5)Oct 21, 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 Engram safe?

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

Does Engram have known CVEs or vulnerabilities?

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

When was Engram last updated?

The latest registry version is 1.10.5, published Oct 20, 2026. The last push to TushaeBXN/engram was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does Engram use?

GitHub reports the license of TushaeBXN/engram as MIT.

Related servers

same publisher / similar score