Case file No.009 · pypi · stdio

PyMemoryEditor

io.github.JeanExtreme002/PyMemoryEditor · v3.4.0

Read, write and scan process memory, Cheat Engine style, on Windows, Linux and macOS.

Package ↗GitHub ↗Website ↗

Security score

100/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 7 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption10/10

10197 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 (v3.4.0)Oct 16, 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 PyMemoryEditor safe?

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

Does PyMemoryEditor have known CVEs or vulnerabilities?

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

When was PyMemoryEditor last updated?

The latest registry version is 3.4.0, published Oct 12, 2026. The last push to JeanExtreme002/PyMemoryEditor was on Oct 12, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does PyMemoryEditor use?

GitHub reports the license of JeanExtreme002/PyMemoryEditor as MIT.

Related servers

same publisher / similar score