Case file No.203 · pypi · stdio

Mergetrain

io.github.yongjip/mergetrain · v3.7.0

Queue parallel-agent worktree branches, test together, serialize and recover Git pushes.

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

598 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

v3.6.0 → v3.7.0Oct 19, 2026
- version changed version bump
```
"3.6.0" → "3.7.0"
```
- packages.0.version changed package version bump
```
"3.6.0" → "3.7.0"
```
- packages.0.runtimeArguments.1.value changed version string inside argument
```
"mergetrain[mcp]==3.6.0" → "mergetrain[mcp]==3.7.0"
```
First snapshot (v3.6.0)Oct 18, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Mergetrain safe?

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

Does Mergetrain have known CVEs or vulnerabilities?

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

When was Mergetrain last updated?

The latest registry version is 3.7.0, published Oct 18, 2026. The last push to yongjip/mergetrain was on Oct 18, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does Mergetrain use?

GitHub reports the license of yongjip/mergetrain as MIT.

Related servers

same publisher / similar score