recurring_select

The popularity rating of recurring_select explained

Github Repository Rubygem
The highest rated repository is rails/rails with 20812 watchers and 7365 forks, resulting in a Github score of 100.00 The highest rated Rubygem is rake with 46371855 total downloads
These are the references for the score, marking the popularity of 100%
Now, the repository for recurring_select over at getjobber/recurring_select has got 88 watchers and 55 forks, resulting in a Github score of 0.61 Now, the gem recurring_select has got 8620 total downloads
Therefore, the relative popularity percentage can be calculated for recurring_select
0.61 watchers & forks * 100% = 0.63%
100.00 top score
8620 total downloads * 100% = 0.02%
46371855 top score
The average of those two values results in the score:

0.31%

So, assuming everyone is using the most popular projects,
roughly one out of 100 Rubyists use recurring_select
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.