Case file No.078 · pypi · stdio

Beadhive

io.github.beadhive/beadhive · v0.28.1

Manage cross-repository beads work, hive status, and Beadhive workflows through bh-mcp.

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 MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1365 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.26.0 → v0.28.1Oct 20, 2026
- version changed version bump
```
"0.26.0" → "0.28.1"
```
- packages.0.version changed package version bump
```
"0.26.0" → "0.28.1"
```
v0.25.4 → v0.26.0Oct 18, 2026
- version changed version bump
```
"0.25.4" → "0.26.0"
```
- packages.0.version changed package version bump
```
"0.25.4" → "0.26.0"
```
First snapshot (v0.25.4)Oct 16, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Beadhive safe?

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

Does Beadhive have known CVEs or vulnerabilities?

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

When was Beadhive last updated?

The latest registry version is 0.28.1, published Oct 20, 2026. The last push to beadhive/beadhive was on Oct 20, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does Beadhive use?

GitHub reports the license of beadhive/beadhive as MIT.

Related servers

same publisher / similar score