Case file No.388 · pypi · stdio

Droste

io.github.lorismascio17/droste-memory · v1.3.0

Local code exploration with progressive zoom and measured token budgets.

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

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

318 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.3.0)Oct 20, 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 Droste safe?

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

Does Droste have known CVEs or vulnerabilities?

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

When was Droste last updated?

The latest registry version is 1.3.0, published Oct 19, 2026. The last push to lorismascio17/droste-memory was on Oct 19, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does Droste use?

GitHub reports the license of lorismascio17/droste-memory as MIT.

Related servers

same publisher / similar score