Case file No.308 · pypi · stdio

Monte-Neo strategy verifier

io.github.NeoZorK/monte-neo · v0.53.2

Verify trading-strategy backtests: look-ahead probes, trading costs, Deflated Sharpe, walk-forward.

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

396 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

v0.53.1 → v0.53.2Oct 20, 2026
- version changed version bump
```
"0.53.1" → "0.53.2"
```
- packages.0.version changed package version bump
```
"0.53.1" → "0.53.2"
```
First snapshot (v0.53.1)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Monte-Neo strategy verifier safe?

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

Does Monte-Neo strategy verifier have known CVEs or vulnerabilities?

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

When was Monte-Neo strategy verifier last updated?

The latest registry version is 0.53.2, published Oct 19, 2026. The last push to NeoZorK/Monte-Neo was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Monte-Neo strategy verifier use?

GitHub reports the license of NeoZorK/Monte-Neo as MIT.

Related servers

same publisher / similar score