Loading devShakib…
Pubspec health for Flutter in VS Code. Discontinued packages, and the plugins still on CocoaPods or blocking AGP 9.
The packages and plugins in your pubspec.yaml that are about to cause trouble — discontinued, retracted, still on CocoaPods, or blocking AGP 9 — flagged on the line you can change.
A pubspec says what you asked for. It doesn't say that one of those packages has been discontinued, that the version pub picked was retracted by its own author, or that a plugin three levels down still has no Swift package — so Flutter falls back to CocoaPods for it, whose registry goes read-only on 2 December 2026. Android has its own version of that: AGP 9's built-in Kotlin fails the build on any plugin that still applies the Kotlin Gradle Plugin. Nothing in the editor says which of your dependencies is the problem. This does.
pubspec.lock was withdrawn by its author.gradle.properties turns it on.Locked versions, not constraints. Pub workspaces are understood: a member is checked against the root's lock, and a sibling package is never looked up on pub.dev, where a stranger may own the name. A 94-app monorepo is checked in under two seconds.
Quick fixes run the upgrade that actually moves the package — pub refuses --major-versions for a package you didn't list, so it upgrades the one you did — or open a pre-filled issue for a plugin's maintainers, which you read and submit yourself. Hovers show pub points, likes and downloads.
Run full health check runs flutter_health_check over the project — store rules, leaked secrets, Firebase rules, vulnerable packages — and writes one report.
The CocoaPods freeze and AGP 9 reach every Flutter app at once, and the fix is usually a single version bump — once you know which plugin. The full list of checks is in the README on GitHub.
MIT licensed, source on GitHub, free like everything else here.