Case file No.036 · pypi · stdio

Ekbasis

io.github.OpenInterpretability/ekbasis · v0.1.42

Foresee what git commands and multi-step changes will do, as calibrated probabilities

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

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

2203 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.1.41 → v0.1.42Oct 17, 2026
- version changed version bump
```
"0.1.41" → "0.1.42"
```
- packages.0.version changed package version bump
```
"0.1.41" → "0.1.42"
```
First snapshot (v0.1.41)Oct 16, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Ekbasis safe?

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

Does Ekbasis have known CVEs or vulnerabilities?

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

When was Ekbasis last updated?

The latest registry version is 0.1.42, published Oct 16, 2026. The last push to OpenInterpretability/ekbasis was on Oct 16, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Ekbasis use?

GitHub reports the license of OpenInterpretability/ekbasis as Apache-2.0.

Related servers

same publisher / similar score