You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to bring to attention an issue with the https://pub.dev website that I've run into a few times in enterprise environments. When using an open-source package, we oftentimes have to justify the use of that package by popularity and maintenance levels. While the "pub score" (formerly the maintenance score) works well for the latter, I have issues presenting a case for the former because pub.dev uses an arbitrary percentage to show popularity.
My superiors are often looking for download statistics (see cargo/npm for examples) and aren't satisfied with a percentage that lies on an unknown scale. As you might imagine, building out a Dart stack without using packages is impossible, so it would be nice to have a clearer indicator of exactly how many users a given package has.
The text was updated successfully, but these errors were encountered:
I wanted to bring to attention an issue with the https://pub.dev website that I've run into a few times in enterprise environments. When using an open-source package, we oftentimes have to justify the use of that package by popularity and maintenance levels. While the "pub score" (formerly the maintenance score) works well for the latter, I have issues presenting a case for the former because pub.dev uses an arbitrary percentage to show popularity.
My superiors are often looking for download statistics (see cargo/npm for examples) and aren't satisfied with a percentage that lies on an unknown scale. As you might imagine, building out a Dart stack without using packages is impossible, so it would be nice to have a clearer indicator of exactly how many users a given package has.
The text was updated successfully, but these errors were encountered: