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
Currently, the application only records a counter of downloads per extension; this isn't ideal as it loses traceability and we don’t know which version of the extension is being downloaded.
If a malicious extension were to be published, it would be essential to understand its impact to enable appropriate action.
My proposal is to use a time-series database for storing download events, providing extension authors with easy-to-use tools. This would also offer a simple and effective way to visualise an extension’s growth over time.
References
A good example of the desired outcome can be seen in npmx.dev's stats tab. Although to achieve that same level of UX/UI we need to switch from MUI charts.
@hacetin AFAIK from openvsx side there's no distinction we can make between a download/install/update for us its just a download, that could only be determined from the IDE side.
fyi: with #2089 there is now also information about the size of each extension stored in the DB. We can use that also for statistics or the extension details page.
Activity
[-]Provide a better extension downloads stats[/-][+]Provide better extension downloads stats[/+]hacetin commentedon Aug 5, 2026
I would like to have this feature as well. We could use it to see trends like downloads/installs/updates and metrics for specific versions.
gnugomez commentedon Aug 8, 2026
@hacetin AFAIK from openvsx side there's no distinction we can make between a download/install/update for us its just a download, that could only be determined from the IDE side.
Please correct me if I'm wrong.
netomi commentedon Aug 24, 2026
fyi: with #2089 there is now also information about the size of each extension stored in the DB. We can use that also for statistics or the extension details page.