How to interpret #downloads of a module on Forge?
Forgive me if this is not the right question to ask here (I'm new to the Forge ecosystem).
For each module, the module page would show the total number of downloads of the module. To me, #downloads are usually a big indicator of popularity (even maturity). If two modules have distinct download times, I tend to first try the one with higher #downloads. Presumably, this is the purpose for Forge to show users the #downloads.
So I'm very curious about how does the Forge count #downloads for each published module? I would guess 1 download means the module is downloaded either from the website (downloading the tarball) or from the client (using puppet module install)? However, such counting cannot tell how many people use the module because it is clearly biased to whom with big clusters. I believe Forge has better way to count the downloads.
The question comes from my recently published module on Forge. It's for a very new and specific software project, and I just find it has got ~250 downloads which does not seem reasonable to me (though I'm happy with the number).
Thank you very much!