Forem

Forem ranks 575th overall in the developer tools category with a composite score of 35 out of 100. The organization describes itself as The open source project behind dev.to. Part of the @MLH family, which frames how developers first encounter the brand on GitHub, in package registries and in search results.

Its documentation and learning material and code quality come across as middling, with room to improve, and are what most developers will notice first when they land on the organization. By contrast, its developer experience and shipping velocity look minimal today, which is the clearest area where a small amount of focused work would visibly move the needle. Taken together, the picture is of a company whose public developer surface is neither uniformly polished nor uniformly weak, and where different audiences (contributors, integrators, evaluators) will likely form very different first impressions depending on which door they walk through.

Forem maintains 21 public repositories on GitHub, built primarily in Ruby, Jinja and Kotlin, which together have collected 25,412 stars and drawn contributions from 15 developers outside the core team, 2 of those repositories have seen commits in the last 90 days, a useful proxy for how much of the codebase is genuinely alive rather than archived.

For anyone evaluating Forem as a technology choice, weighing a contribution, integrating the APIs, or comparing it against similar companies in the space, the sections below break down each of these signals in detail and link straight through to the underlying repositories, documentation and community threads that inform the score.