Case file No.020 · pypi · stdio

Repowise

dev.repowise/repowise · v0.58.0

Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.

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

4912 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.57.0 → v0.58.0Oct 21, 2026
- version changed version bump
```
"0.57.0" → "0.58.0"
```
- packages.0.version changed package version bump
```
"0.57.0" → "0.58.0"
```
First snapshot (v0.57.0)Oct 16, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Repowise safe?

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

Does Repowise have known CVEs or vulnerabilities?

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

When was Repowise last updated?

The latest registry version is 0.58.0, published Oct 20, 2026. The last push to repowise-dev/repowise was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does Repowise use?

GitHub reports the license of repowise-dev/repowise as AGPL-3.0.

Related servers

same publisher / similar score