What it checks
- Discontinued packages. Authors can mark a package as discontinued on pub.dev and name a replacement, such as
uni_linkspointing toapp_links. A discontinued package gets no fixes, so plan to move off it first. - New versions outside your constraint. If the latest version doesn’t fit your version constraint,
flutter pub upgradewon’t install it. The checker shows the version to use and marks major updates, which can contain breaking changes. - Dart 3 compatibility. Dart 3 requires sound null safety, so a package that isn’t Dart 3 compatible won’t build with current Flutter versions.
- Maintenance signals. When the package was last published, its pub points, likes and supported platforms. A package with no release in two years isn’t always broken, but it is a risk worth checking.
- Packages pinned by Flutter. Some packages, such as
intl, are pinned by the Flutter SDK itself. Raising them by hand fails to resolve; upgrading Flutter brings the new version.
Reading version constraints
Most pubspecs use caret syntax.^2.4.0 means “2.4.0 or newer, but below 3.0.0”, so flutter pub upgrade moves you to the newest 2.x release on its own. For versions below 1.0, the caret is stricter: ^0.6.18 means “below 0.7.0”, because in 0.x versions a minor bump can break things. That’s why the checker reports 0.19 to 0.20 as a major update.
How to upgrade safely
- Work on a branch and make sure the app builds and its tests pass before you change anything.
- Replace discontinued packages first. They usually need code changes, and they won’t get fixes for new Android or iOS versions.
- Upgrade one major version at a time and read each package’s changelog. Run
flutter pub get, thendart fix --apply, which applies many API migrations for you. - Use
flutter pub upgrade --major-versionsonly when you want every constraint raised at once; on a big app it’s easier to find what broke when you go package by package. - Test on real Android and iOS devices before you release, especially plugins with native code such as Firebase, maps or payments.
The command-line equivalent is flutter pub outdated, which compares your resolved versions with the newest ones. This checker adds discontinued status, replacements, Dart 3 readiness and maintenance signals in one view, and works without a project on your machine. For the bigger picture, see the Flutter app maintenance checklist.
Questions
Is my pubspec sent anywhere?
No. The pubspec is read in this page. To look packages up, the tool sends only each package’s name to pub.dev’s public API, the same data you see on pub.dev.
Should I always upgrade to the latest version?
Not blindly. Patch and minor updates within your constraint are usually safe. Major updates can change APIs and need code changes and testing, so plan them. Replacing discontinued packages and fixing Dart 3 issues comes first.
Why does it say a package is pinned by Flutter?
Packages like intl and collection are fixed to a specific version by the Flutter SDK. If you raise them in your pubspec, dependency resolution fails. Upgrade Flutter itself and these packages follow.
What are pub points?
Pub points are pub.dev’s score, out of 160, for following Dart conventions, documentation, platform support, passing static analysis and supporting up-to-date dependencies. See how pub.dev scores packages. Low points are a hint to look closer, not proof that a package is bad.
Need an old Flutter app brought up to date and released again? I’m Muhammad Naeem, a Flutter developer with 10+ apps live on the stores. See app maintenance or tell me about your project.