The packages service currently keeps a single point-in-time snapshot of download counts for a package, it would be great to track that over time so we can chart the changes of downloads.
This probably make sense to be in the packages service but may need slightly different infrastructure than just storing it directly in postgresql along side all the other data.
Potentially can also store per-version download data if it's available in that ecosystem.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
The packages service currently keeps a single point-in-time snapshot of download counts for a package, it would be great to track that over time so we can chart the changes of downloads.
This probably make sense to be in the packages service but may need slightly different infrastructure than just storing it directly in postgresql along side all the other data.
Potentially can also store per-version download data if it's available in that ecosystem.
Upvote & Fund