Case file No.376 · pypi · stdio

LineBreak Gate & Spec Bridge

com.linebreakapp/linebreak-gate · v1.10.3

Approved acceptance criteria served over MCP to Claude Code, Cursor, or Codex. Git-only, sealed.

Package ↗GitHub ↗Website ↗

Security score

85/100

Strong

Normalized over 80 points of available evidence.

Unknown: Maintenance

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Source transparency10/15

public repo, license unknown/none

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

136 weekly downloads

Maintenanceunknown

Excluded from the score — no data available.

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 (v1.10.3)Oct 24, 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 LineBreak Gate & Spec Bridge safe?

MCPWatch gives LineBreak Gate & Spec Bridge a heuristic security score of 85/100 (strong), based on 80 points of available evidence; unknown: Maintenance. This is an automated heuristic, not an audit.

Does LineBreak Gate & Spec Bridge have known CVEs or vulnerabilities?

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

When was LineBreak Gate & Spec Bridge last updated?

The latest registry version is 1.10.3, published Aug 11, 2026. The last repository push is unknown. MCPWatch last checked it on Oct 24, 2026.

What license does LineBreak Gate & Spec Bridge use?

Unknown — GitHub metadata was not available on the last refresh.

Related servers

same publisher / similar score