Case file No.337 · pypi · stdio

Twin Me Up

io.github.GitDakky/twin-me-up · v0.2.1

A personal work twin for every AI agent: your confirmed guidance and explicit grants, enforced.

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 4 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

358 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.2.1)Oct 17, 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 Twin Me Up safe?

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

Does Twin Me Up have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package twin-me-up. That is not proof of safety.

When was Twin Me Up last updated?

The latest registry version is 0.2.1, published Oct 15, 2026. The last push to GitDakky/twin-me-up was on Oct 16, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Twin Me Up use?

GitHub reports the license of GitDakky/twin-me-up as Apache-2.0.

Related servers

same publisher / similar score