Case file No.325 · pypi · stdio

OpenLeads

io.github.Samyrrrrrr990/openleads · v5.0.0

Find leads with honest email evidence, then work them: CRM, sequences, tasks, deals. No API keys.

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

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

375 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

First snapshot (v5.0.0)Oct 17, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is OpenLeads safe?

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

Does OpenLeads have known CVEs or vulnerabilities?

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

When was OpenLeads last updated?

The latest registry version is 5.0.0, published Oct 15, 2026. The last push to Samyrrrrrr990/openleads was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does OpenLeads use?

GitHub reports the license of Samyrrrrrr990/openleads as AGPL-3.0.

Related servers

same publisher / similar score