Do RubyGems from GitHub have different reliability compared to RubyForge packages?

I’ve been wondering about the quality differences between gems hosted on different platforms. When I was working on a Ruby project recently, I noticed that some gems come from GitHub repositories while others were traditionally hosted on RubyForge.

My thinking was that RubyForge gems might be more stable and official since they seemed to go through a more formal release process. But someone told me this might not be true.

What’s your experience with this? Do developers typically use GitHub for quick releases and experimental versions, saving the stable stuff for RubyForge? Or is the difference in release frequency more about convenience and ease of use rather than stability?

I’m trying to figure out if I should prefer one source over another when choosing gems for production applications.

From my experience with production Rails apps, hosting platform doesn’t affect reliability at all. I’ve seen buggy gems from formal release processes and rock-solid ones built entirely on GitHub. What matters is maintenance quality and community support. For production gems, I check documentation quality, recent updates, proper semantic versioning, and whether maintainers handle security issues quickly. GitHub actually gives better visibility here - you can see the actual dev workflow, how they handle PRs, and whether they’re running CI/CD tests. Everyone moved from RubyForge because GitHub has better collaboration tools, not because the gems got less reliable.

totally agree! rubyforge’s pretty much abandoned. these days, github’s where most of the action’s at. their releases seem more dependable since u can track the history and read issues directly.

RubyForge died years ago, so this comparison doesn’t matter anymore. Everyone moved to GitHub and RubyGems.org - that’s the standard now. Don’t worry about hosting platforms when checking if a gem’s reliable. Look at commit activity, contributor count, test coverage, and how fast maintainers fix issues. GitHub gems are usually more transparent since you can see everything - the dev process, pull requests, how quickly maintainers respond to bugs. That formal RubyForge release process didn’t make gems more stable anyway. What matters is the maintainer’s habits and how mature the gem is.