Inspect dependency versions, outdated packages, duplicates, and vulnerability reports in Flame IDE. Review wanted and latest versions and run scoped updates.
An outdated package is a decision, not just a badge. You need to know the installed version, the allowed upgrade, the newest release, and whether an advisory changes the priority. Flame's Dependencies panel puts that package context beside the source and keeps each update attached to the project where it started.
Inspect declared constraints and resolved versions where available. Supported ecosystems include npm, Cargo, pip, Go, Composer, Bundler, Maven, Gradle, and Dart pub, with capabilities varying by toolchain.
Compare current, wanted, and latest versions. Select update targets deliberately instead of treating an in-range update and a major upgrade as the same action.
Read available audit findings, inspect duplicates and size information when supported, create reports, or prepare an AI security-fix conversation with the relevant context.
Select a project with a supported package manifest and open Dependencies. Flame detects applicable ecosystems and workspace members. Install the project's required package-manager tools on the host.
Review the dependency list, outdated results, and security findings. A missing or unavailable check is not a clean result. Use Refresh when you need a fresh check rather than cached package-manager output.
Select the packages and wanted or latest targets you intend to install. Start the update and watch its progress. If you switch projects while it runs, the operation stays bound to the original project.
Review manifest and lockfile changes in Git, run the project's tests, and inspect the application. Refresh the dependency checks to confirm the expected versions and findings.