flutter-firebase
Pass
Audited by Gen Agent Trust Hub on Sep 15, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: No security issues detected. The skill strictly follows industry best practices for mobile backend integration.
- [CREDENTIALS_SAFE]: The instructions mandate the use of
flutter_secure_storagefor authentication tokens and explicitly warn against storing credentials in source code or insecure local storage likeSharedPreferences. - [DATA_EXPOSURE_SAFE]: The skill includes a specific prohibition against logging Personally Identifiable Information (PII) such as emails, passwords, and phone numbers in analytics events, which prevents accidental data leakage.
- [PRIVILEGE_ESCALATION_SAFE]: The guidelines for Firestore persistence advocate for a "default deny" security posture, requiring developers to explicitly open access only when necessary and validating authentication state via server-side rules.
- [INDIRECT_PROMPT_INJECTION]: As this skill consists of static development guidelines and best practices, it does not ingest untrusted external data or provide a surface for prompt injection attacks.
- [COMMAND_EXECUTION_SAFE]: The skill recommends the use of official tooling, specifically
flutterfire configure, for platform-specific setup, which is the standard, documented process for Firebase integration.
Audit Metadata