Why does this project feel abandoned? (Part 2 — Checking in for 2026)

Hi everyone,

First, I want to express my gratitude to the contributors of single-spa. This framework has been a cornerstone of the micro-frontend ecosystem for years, and the work done here has paved the way for how many of us build scalable web applications.

I am currently evaluating the framework for a new long-term project and, after performing some due diligence on the current health of the repository, I have a few concerns regarding its maintenance status in 2026. I am opening this issue in a spirit of transparency and helpfulness for the community, not to offend or criticize.

Observations:

• v7.0 Development: The 7.0 branch saw significant activity in 2025 (specifically around September 2025), but development seems to have paused since then.
• Main Branch Activity: The last "core" logic merge to the main branch appears to have been in late 2024.
• Community Infrastructure: Several users have noted that the Slack invitation links (the primary community hub) are currently non-functional (referenced in Issue #1328).
• Ecosystem Compatibility: With recent major updates to peer frameworks (React 19, Angular 18/19, Vue 3.x), there is concern about whether the current single-spa helpers will continue to be patched for breaking changes.

My Questions:

1. Is there an active maintainer currently overseeing the transition from the v7.0 beta to a stable release?
2. Is the project currently in "maintenance mode" (critical security fixes only) or "active evolution"?
3. Is there a preferred way for the community to help revive the Slack/communication channels?

I would prefer to stay within this ecosystem, but as we move further into 2026, we need to understand the risk profile for production support.

Any insight from the core team or current contributors would be greatly appreciated.

Best regards,

Wouter