A browser extension that detects Flutter-powered websites and reveals the Dart packages behind them.
Flutter web applications don't expose the same kind of readable HTML structure that developers normally rely on when inspecting a website.
When I wanted to understand whether a website was built with Flutter - and what packages or plugins it might be using - the process involved manually inspecting assets, bundles, and network activity.
I wanted a faster way to answer a simple question: How was this Flutter website built?
Flutter Recon is a browser extension that performs a lightweight analysis of the current webpage to determine whether it is powered by Flutter.
When Flutter is detected, the extension identifies referenced Dart and Flutter packages and presents them in a simple interface. Each discovered package can then be opened directly on pub.dev .
What would normally require several manual inspection steps becomes a quick lookup from the browser.
The extension works by inspecting publicly available information exposed by the page and its loaded assets.
Flutter's web runtime doesn't make package discovery as straightforward as inspecting dependencies in a traditional HTML-based application.
The extension therefore relies on browser extension APIs and runtime information exposed by the target page rather than requiring access to the website's source code or backend.
The entire process is read-only. Flutter Recon doesn't modify the target website, collect user data, or require access to authenticated areas.
This project started from curiosity.
I came across Flutter-powered websites and wanted an easier way to understand what was happening behind the interface. Instead of repeatedly performing the same inspection manually, I turned the process into a small developer tool.
It's useful for developers exploring unfamiliar implementations, researching technologies used by a website, or simply satisfying the question of "how did they build this?"
Building Flutter Recon gave me hands-on experience with browser extension APIs, client-side inspection, runtime detection, and extracting useful information from compiled web applications.
It also reinforced something I enjoy about development: finding a repetitive or frustrating investigation process and turning it into a small tool that makes the answer easier to find.
The complete source code, documentation, and installation instructions are available on GitHub.
