How healthy are your dependencies?
Paste a pubspec.yaml, a pubspec.lock or a list of package names. Each dependency gets a verdict from daily data on 5,003 pub.dev packages, with the reasons behind it.
How verdicts work
The first rule that matches wins. The score is the share of judged direct dependencies that are Healthy or Stable; the grey states are left out of it. Verdicts never guess: missing data means no verdict.
- Replace now
- Discontinued on pub.dev, or its GitHub repo is archived.
- At risk
- Low activity, and not finished enough to call Stable.
- Watch
- Activity is slowing, and not finished enough to call Stable.
- Healthy
- Committed to within 30 days and released within 120.
- Stable
- Quiet, but finished: 140+ pub points, a release within 3 years, and downloads not falling.
- Not enough data
- Tracked, but a date a rule needs is missing, so no verdict is given.
- Not tracked
- Not among the packages Flutterverse tracks, so there’s nothing to judge it on.
- Not checked
- A git, path or private-registry dependency: only pub.dev packages are checked.
↑ Rising marks Healthy or Stable packages with a momentum score of 75 or more.