Case file No.089 · pypi · stdio

AdversaryGate

io.github.Sanflow10/adversary-gate · v3.0.14

Fail-closed merge gate an agent calls before saying done: MERGE, BLOCK or INCONCLUSIVE.

Package ↗GitHub ↗Website ↗

Security score

96/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 AGPL-3.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1204 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.0.10 → v3.0.14Oct 19, 2026
- version changed version bump
```
"3.0.10" → "3.0.14"
```
- packages.0.version changed package version bump
```
"3.0.10" → "3.0.14"
```
v3.0.9 → v3.0.10Oct 18, 2026
- version changed version bump
```
"3.0.9" → "3.0.10"
```
- packages.0.version changed package version bump
```
"3.0.9" → "3.0.10"
```
First snapshot (v3.0.9)Oct 16, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is AdversaryGate safe?

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

Does AdversaryGate have known CVEs or vulnerabilities?

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

When was AdversaryGate last updated?

The latest registry version is 3.0.14, published Oct 19, 2026. The last push to Sanflow10/adversary-gate was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does AdversaryGate use?

GitHub reports the license of Sanflow10/adversary-gate as AGPL-3.0.

Related servers

same publisher / similar score