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.
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.