Case file No.265 · pypi · stdio

gitpro

io.github.Yantrakar/gitpro · v0.4.1

Read-only checks of which git name, email and SSH key a repository uses, and why.

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

478 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.4.0 → v0.4.1Oct 19, 2026
- version changed version bump
```
"0.4.0" → "0.4.1"
```
- packages.0.version changed package version bump
```
"0.4.0" → "0.4.1"
```
First snapshot (v0.4.0)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is gitpro safe?

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

Does gitpro have known CVEs or vulnerabilities?

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

When was gitpro last updated?

The latest registry version is 0.4.1, published Oct 18, 2026. The last push to Yantrakar/gitpro was on Oct 18, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does gitpro use?

GitHub reports the license of Yantrakar/gitpro as MIT.

Related servers

same publisher / similar score