Any way to get install statistics? #39736
Replies: 5 comments 16 replies
-
This should probably get moved to https://github.com/microsoft/winget-cli (@denelon) AFAIK winget cli does contact the database everytime you run There have however been a request for a logo/icon in the manifest microsoft/winget-cli#1253, so maybe we'll get a different front-end in the future |
Beta Was this translation helpful? Give feedback.
-
We do have some telemetry (assuming the OS and the client are configured to provide it). We use it primarily for troubleshooting and identifying errors and failure scenarios. This hasn't been vetted from a privacy or legal standpoint for external use. I'll start the discussions to see if there is some data we can provide. |
Beta Was this translation helpful? Give feedback.
-
We don't get "all" install statistics. We only sample the data. As we've been discussing the mechanisms and governance concerns around sharing this kind of data, we've identified a few areas of concern. Publishers would need to have access to something to get this kind of data and should be able to decide if they are OK sharing the data. This data is available to Microsoft Store publishers today via Partner Center. As we continue to work on verified developer, this topic will be a part of the discussion. The main concern is how we verify developers and provide mechanisms for them to manage which GitHub aliases are authorized to make changes to the "allowed" list of users. That would also potentially be a good place for publishers to acquire the data and make the decision if they are comfortable with making the sampled data available to the public. |
Beta Was this translation helpful? Give feedback.
-
How is this still an issue? |
Beta Was this translation helpful? Give feedback.
-
Any statistics we could publish would be based on samples, so the results would not necessarily be accurate/complete. Who would the data be for? Publishers: I've had a few discussions with @JanDeDobbeleer about the data for Oh-My-Posh as a publisher. I've also talked with a few other publishers, so I believe I understand what is being asked for from that perspective. The main challenge is a business process challenge to ensure we're only providing that kind of detailed data to an authorized party with some kind of agreement (or to support a proper mechanism for opt-in/opt-out). That's why I mentioned Partner Center earlier. I'm not aware of any "official" way to validate the identity of another publisher/organization who choose not to participate in the GitHub ecosystem where the community repository "lives" without integrating with some other identity provider(s). WinGet Users: Is this about helping a user find "the best (success/failure rates/percentages)" or "the most popular (search, install, upgrade, uninstall rates/percentages/counts)" package? What questions does the data help a customer answer? What kind of UX makes sense for the CLI experience? UniGetUI (@marticliment) and Dev Home as two example UIs integrating with WinGet would likely leverage COM APIs to get the data from WinGet rather than a separate web service. Other Concerns Is this work more important/valuable than other features/bug fixes? I'm happy to break this down into some smaller bite sized pieces of work we can start digging into. I just need to understand the cost/benefit equation(s) associated with doing this work vs. other work. I also want to make sure we build the right thing. If I understand the questions/needs, then I can also look to see if there are other ways to provide enough data/information to help users make informed decisions. |
Beta Was this translation helpful? Give feedback.
-
The title says it all, I’m looking for a way to understand how many time a package is downloaded, installed, searched,… Couldn’t find anything about this, might not yet exist.
Beta Was this translation helpful? Give feedback.
All reactions