I sent the fixes. A month later, none of them have merged.

Description and use

The author reported 18 broken Pipecat plugins, but after review only 13 were truly broken; the rest were due to strict version pins or licensing. PRs remained unmerged, highlighting a maintenance gap.

Problem

Community plugins for Pipecat were reported broken, but submitted fixes remained unmerged after a month.

Outcome

The initial claim of 18 broken plugins was refined to 13 genuine breakages, revealing that six were misclassified due to pinning or licensing. No PRs were merged, highlighting a gap in community plugin maintenance workflows.

Workflow

• 1. Published initial count of broken plugins. 2. Submitted eleven PRs to fix import errors and dependency issues. 3. Monitored PR status for a month. 4. Reader Arhan Canli identified mis‑categorized plugins. 5. Ran tests with --no-deps and uv --overrides to differentiate pin‑tight vs. API break. 6. Updated table to reflect 13 genuinely broken plugins, 5 pin‑tight, 1 licensed‑SDK. 7. Reflected on reasons for lack of PR merges and suggested CI and health badges.

Evidence

Every one is still open. Every one is mergeable, not a draft, with no conflicts and nothing red.

Source

Nine of eleven have had no human response at all.

Source

The pinned five are the only group where nothing has been shown to be broken.

Source

All five were fine. Zero are broken.

Source

Six of the plugins I called broken were working the whole time.

Source