- Home
- Skills
- Mobile Development
- Flutter App Safety Check
More screenshots
Works with the AI Agents you already use
Flutter App Safety Check
This skill finds those and eleven other Flutter and Dart mistakes before you ship, and tells you how to fix each one.
$5
Flutter App Safety Check
Example session with this skill installed
Check this project with flutter-app-safety-check.
- Read your context and instructions
- Compiled the flutter app safety
$ python3 scripts/check_flutter.py examples/risky
BLOCK lib/config.dart:3 F03 CLEARTEXT_HTTP_ENDPOINT
static const apiBaseUrl = 'http://api.fastcart-demo.com/v2';
Why: The app talks to a server over http:// or ws://, so requests and responses (tokens, personal data, orders) travel unencrypted and can be read or changed on public Wi-Fi. Dart's built-in HttpClient, which package:http and dio use on Android and iOS by default, does not enforce Android's cleartext setting or iOS App Transport Security, so nothing stops the request.
Safer: Use https:// and wss:// for every server. If the address differs per environment, pass it with --dart-define. Addresses on the device or emulator (localhost, 127.x, 10.0.2.2, 10.0.3.2) and example domains are not reported; private-network addresses are reported as F19.
BLOCK lib/config.dart:5 F01 SECRET_IN_APP_CODE
BLOCK lib/services/api_client.dart:15 F02 TLS_CHECK_DISABLED
BLOCK pubspec.lock:17 F04 PACKAGES_OVER_HTTP
BLOCK pubspec.yaml:23 F04 PACKAGES_OVER_HTTP
REVIEW lib/config.dart:8 F19 CLEARTEXT_LAN_ENDPOINT
REVIEW lib/data/order_history.dart:9 F18 SQL_BUILT_FROM_VALUES
REVIEW lib/screens/promo_page.dart:14 F16 WEBVIEW_JS_BRIDGE_ON_REMOTE_PAGE
REVIEW lib/services/api_client.dart:18 F12 SECRET_IN_LOGS
REVIEW lib/services/api_client.dart:26 F12 SECRET_IN_LOGS
REVIEW lib/services/session_store.dart:8 F11 TOKEN_IN_PLAIN_STORAGE
REVIEW pubspec.yaml:14 F14 UNBOUNDED_DEPENDENCY_VERSION
REVIEW pubspec.yaml:16 F14 UNBOUNDED_DEPENDENCY_VERSION
REVIEW pubspec.yaml:21 F13 GIT_DEPENDENCY_NOT_PINNED
REVIEW pubspec.yaml:32 F15 DEPENDENCY_OVERRIDES
REVIEW pubspec.yaml:37 F17 SECRET_FILE_IN_ASSETS
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 9 files, 9 with Flutter or Dart content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
client.badCertificateCallback = (cert, host, port) => true, added once for a staging server, or an API secret in lib/config.dart: both ship inside every APK and IPA you release, where anyone can pull them out or sit between your users and your server. This skill finds those and eleven other Flutter and Dart mistakes before you ship, and tells you how to fix each one.
Your agent runs a scanner on your Dart code, pubspec.yaml and pubspec.lock. It reads Dart as Dart (comments, raw and triple-quoted strings, $name and ${...} interpolation), skips tests, generated files and build folders, and knows the usual guards: if (kDebugMode), assert, a navigation allow list, ? placeholders in SQL. Keys meant to ship in apps (Firebase, Google Maps, Stripe publishable, Supabase anon, Algolia search-only) are not reported; a Supabase service_role key is, even under a harmless name, because the scanner reads the role inside the key offline. It never runs flutter, pub or your app. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- F01: secrets compiled into the app (known key formats, Supabase service_role keys, long values in secret-named fields, fixed Authorization headers, keys in URL queries, Gemini keys, String.fromEnvironment defaults)
- F02: badCertificateCallback or onBadCertificate returning true, and WebView SSL errors that always proceed
- F03: http:// and ws:// servers on the public internet
- F04: packages downloaded over http:// or git://
REVIEW
- F11: tokens and passwords saved in shared_preferences, GetStorage or an unencrypted Hive box
- F12: tokens printed with print or debugPrint, and HTTP loggers left on in release builds
- F13: git dependencies without a ref or pinned to a branch
- F14: any versions, missing versions and open-ended ranges
- F15: dependency_overrides left in pubspec.yaml
- F16: WebView JavaScript channels on remote pages without a navigation allow list
- F17: .env, key and credentials files bundled as Flutter assets
- F18: sqflite and drift SQL built with string interpolation
- F19: http:// and ws:// to private-network addresses (192.168.x.x, .local, .lan, .internal) outside debug builds
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example Flutter project, and the real report the scanner produces on the risky one
Limits It reads each file on its own: values passed between files, platform code in android/ and ios/ (check the manifest and Info.plist separately), native plugins and known vulnerabilities in package versions are not checked. NOT FLAGGED is not a guarantee.
Static check of Dart and pubspec text, one file at a time. The Android manifest, iOS Info.plist and runtime settings are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes a clearly fake, inert secret (not-a-real-...) and fake Firebase values for the scanner to read. It is never run.