Update on js-libp2p maintenance

[aschmahmann]

Per the announcement on the Shipyard blog, (https://ipshipyard.com/blog/2025-libp2p-maintenance-update/), Shipyard will be transitioning stewardship of js-libp2p to community maintainers.

Shipyard will continue active maintenance of js-libp2p until September 30, 2025, while working with credible community members or organizations with a proven track record to ensure a smooth handoff. We are committed to helping place these critical implementations in capable hands.

We’ve been proud to steward js-libp2p under Shipyard, and we’re grateful for the many contributors who’ve helped make js-libp2p what it is today. If you’d like to be involved in the transition please comment here or reach out to us directly.

[Faolain]

Is there a number on what it costs to maintain libp2p support and/or do team members who cannot support it with current resources have a desire to continue maintenance if funding can be met? There are a variety of means to meet these gaps imo and for teams that rely on the tooling underpinning libp2p I think it's important to know this.