Case file No.324 · npm · stdio

Labby

ai.dinglebear/labby · v2.6.2

Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI.

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

115 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 (v2.6.2)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 Labby safe?

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

Does Labby have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the npm package @dinglebear/labby. That is not proof of safety.

When was Labby last updated?

The latest registry version is 2.6.2, published Oct 10, 2026. The last push to dinglebear-ai/labby was on Oct 24, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Labby use?

GitHub reports the license of dinglebear-ai/labby as AGPL-3.0.

Related servers

same publisher / similar score