Case file No.041 · npm · stdio

Memorix

io.github.AVIDS2/memorix · v1.10.1

Local-first project memory with legacy MCP and 2026 discovery compatibility.

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

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

960 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

v1.9.11 → v1.10.1Oct 24, 2026
- version changed version bump
```
"1.9.11" → "1.10.1"
```
- packages.0.version changed package version bump
```
"1.9.11" → "1.10.1"
```
First snapshot (v1.9.11)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Memorix safe?

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

Does Memorix have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the npm package memorix. That is not proof of safety.

When was Memorix last updated?

The latest registry version is 1.10.1, published Oct 23, 2026. The last push to AVIDS2/memorix was on Oct 23, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Memorix use?

GitHub reports the license of AVIDS2/memorix as Apache-2.0.

Related servers

same publisher / similar score