Skip to main content

Dependency health

Dependency health flags packages your repositories pin that are not vulnerable but are a problem all the same. A version-update bot cannot see these, because it follows a package name.

KindWhat it meansWhere the signal comes from
MovedThe project went on under another package while the one you pin stopped. fremforge flags a move only when a successor is named (Renovate’s replacement, or a package from the same source repository that installs the same command, or the only package from that repository on its latest major) and the old package stopped: its repository is on a major it never published, it has had no release for 30 days while the repository kept releasing, or the repository is archived. A renamed or redirected repository on its own is not a movefremforge compares the package with its source repository on GitHub
DeprecatedThe registry marks the package deprecatedThe registry’s own deprecation flag and message
AbandonedNo release for 12 months, and the project shows it has stopped: its repository is archived or disabled, has had no commit for 24 months, or says it is unmaintained, deprecated or looking for maintainersHosted Renovate’s release dates, and the source repository on GitHub
StaleNo release for 12 months, but nothing says the project has stopped (or there is no source repository to check). Information onlyHosted Renovate’s release dates

The findings are in Security › Findings › Dependencies › Health. Each one says what happened in plain language, for example “Last stable release 1.19.5 on 28 Oct. The project is now at 2.2.6 under @opencode/cli.”. When fremforge can tell which package replaced it, the finding suggests that package and gives the install command. They are also listed under the Dependency health type in Findings › All.

Dependency health currently needs hosted Renovate: findings appear only for repositories that take part in Version updates, because the checks run with every Version updates run. Turn Version updates on for a repository to see its dependency health.

Stale findings are information only: they have their own filter in the Health tab, are not counted under All or in Findings › All, and are never mailed, sent to webhooks or sent to your SIEM.

Dismissing a finding

Dismiss a finding with a reason, and optionally an end date, the same way as other dependency findings. If your organisation requires approval for dismissals, the dismissal goes to Exceptions. A dismissed finding comes back when its end date passes, and you can reopen it from Dismissed.

Notifications

New and reopened findings appear in the daily alert summary. The Dependency health email is on by default for the organisations you own, and off where you are a member. You get one email per organisation per day, at 07:00 Copenhagen time and only when there is a new or reopened finding, and the daily summary links to it instead of repeating it. To stop it, follow the link at the end of any of these emails, or switch Dependency health email off in your notification settings: it then stays off for every organisation. Switch it on there to get it for the organisations where you are a member too; a member’s email gives the number of findings, not the findings themselves.

The abandonment threshold

12 months by default. To change it for one repository, set abandonmentThreshold in its renovate.json, for example "abandonmentThreshold": "24 months". Set it to null to switch the check off there. A package past the threshold is abandoned only with a second signal from its source repository (archived or disabled, no commit on the default branch for 24 months, or an “unmaintained” notice in its description or at the top of its README); otherwise it is stale. A newer release within the threshold, of any version, means the package is neither. When the package publishes a new release, fremforge clears an abandoned or stale finding for it within an hour of recording that release.

Telling fremforge where a package comes from

To spot a move, fremforge needs the package’s source repository. It looks in three places, in this order:

  1. the package’s registry metadata (for npm, its repository field);
  2. .fremforge/dependency-sources.json in your repository;
  3. a packageRules entry with sourceUrl in your Renovate config, for a rule that names the package literally in matchPackageNames or matchDepNames. fremforge reads the first JSON config file it finds on the default branch (renovate.json, .renovaterc.json, .renovaterc, or renovate.json under .github/, .gitea/ or .forgejo/); a .json5 config is not read for this.

Some packages publish no repository at all. List those in .fremforge/dependency-sources.json on the default branch:

{
  "sources": [
    { "package": "opencode-ai", "ecosystem": "npm", "repo": "anomalyco/opencode" },
    { "package": "internal-tool", "repo": "https://github.com/example/internal-tool" }
  ]
}

package is the name as your manifest pins it. ecosystem is optional; use it when the same name exists in two registries (npm, pypi). repo is owner/name on github.com, or a github.com URL. fremforge reads the file at the next run. An entry it cannot read is skipped and the rest still count. The file is read up to 1 MiB and 1,000 entries.

Moved and abandoned checks read the source repository on github.com; moved checks cover npm and PyPI packages. When a repository publishes tags instead of GitHub releases, or its newest release is more than 180 days old, its newest tag counts as its latest version. Each run checks at most 40 packages, the never-checked and least recently checked first, and a result is reused for 7 days, so the first checks of a large repository are spread over a few runs. fremforge searches for the replacement of a moved package on npm only. For a deprecated package, the suggestion comes from Renovate’s own replacement rules, which also cover other ecosystems.