Case file No.241 · pypi · stdio

Dejo

io.github.dejohq/dejo-mcp · v0.1.2

A browser your AI agent remembers. Learn a site once, replay it in one call, zero model calls.

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 MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

532 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.1.2)Oct 19, 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 Dejo safe?

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

Does Dejo have known CVEs or vulnerabilities?

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

When was Dejo last updated?

The latest registry version is 0.1.2, published Oct 18, 2026. The last push to dejohq/dejo-mcp was on Oct 20, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does Dejo use?

GitHub reports the license of dejohq/dejo-mcp as MIT.

Related servers

same publisher / similar score