A couple of month's ago, I started using cal.com to schedule X Spaces and 1:1s after writing about it in my 29 Days of OSS Alternatives Series. Now, I'm revisiting some of those projects to see how they're doing today.
Single metrics never tell the whole story. Considering a combination of relevant data points help us to understand a more comprehensive picture. While star count (30.5k for cal.com) might indicate popularity, it doesn't tell the whole story. The steady weekly contributor count (19 on average, with 78 outside contributors over the last 30 days), speaks to a story of a positive contributor experience and sustained development activity. The balance of open to closed issues (129 to 115) and the volume of pull requests (245 open) may indicate active maintenance and community engagement.
Meanwhile, the OpenSSF score of 7.5/10 provides insight into the project's security practices. By examining these metrics together, we can better understand cal.com's overall health, community dynamics, and potential for long-term success.
📣 Discuss
- What combination of metrics do you find most helpful in understanding a project and why?
- What are you using to schedule?
Top comments (0)