Transparency around update cadence of data

[jasminewang0]

It would be helpful for users to know how often package data is scheduled to be updated. I see that packages' "last synced" data ranges from <1 min ago to several months ago (ex. deprecated NPM package sntp). It is reasonable for deprecated packages to be synced less often, but I would love to have more information on:

1. what cadence packages are synced on (I am assuming regularity is based on package usage?)
2. when the next sync of a package will be

prior to taking dependencies.

Thank you!

[andrew]

Thanks for reporting, deprecated npm packages not being synced is a bug, I’m not actively syncing packages marked as removed, deprecated packages probably got caught up in that as well, I’ll fix that tomorrow and resync all deprecated npm pkgs.

I’ll get to work on documenting the syncing approach right after FOSDEM as well.

Basically I try to sync the most popular packages every couple of days, every active package should be synced within 1 month, also syncing packages when new releases are detected in registries that have an api for listing recent packages, which are checked multiple times per day.

I’m also watching git repos for releases and tags and then check packages for new releases if and when the repos are updated.

[jasminewang0]

Thanks Andrew! Could you link the syncing documentation when it's up?