Why a feed
The old dependencies page was a table: every package your projects declare, with a badge when it was behind. It answered "what is out of date", which is rarely the question. The question is "what happened to my dependencies since I last looked", and a table has no answer for "since".
The feed reads like a news page instead, newest first:
- Releases of the packages a followed project declares, with their release notes and what changed since the version you are on.
- Deprecations, when a maintainer marks a version or a whole package as deprecated.
- Security advisories that affect the version range you declare. Releases can be muted per package or per major version; advisories never can.
What it reads, and what it does not
Tracking is off by default and turned on per project. A project that is off is never read from GitHub, and turning it off deletes what was stored about it.
Only the manifest is read: what package.json declares, never the lockfile and never transitive dependencies. A range that cannot be read without ambiguity, such as workspace:*, a git URL or latest, is shown as not checked rather than guessed at:
{
"dependencies": {
"react": "^19.1.0",
"shared-ui": "workspace:*"
}
}
Here react is checked against every published version, and shared-ui is reported as not checked. Saying it is up to date would be a guess.