firebase_auth 5.3.4 firebase_auth: ^5.3.4 copied to clipboard
Flutter plugin for Firebase Auth, enabling authentication using passwords, phone numbers and identity providers like Google, Facebook and Twitter.
We analyzed this package 4 days ago, and awarded it 160 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: BSD-3-Clause
.
10/10 points: 20% or more of the public API has dartdoc comments
293 out of 327 API elements (89.6 %) have documentation comments.
Some symbols that are missing documentation: firebase_auth
, firebase_auth.ActionCodeInfo.data
, firebase_auth.ActionCodeInfo.operation
, firebase_auth.AppleAuthProvider.PROVIDER_ID
, firebase_auth.AppleFullPersonName
.
10/10 points: Package has an example
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ macOS
-
✓ Web
These platforms are not supported:
Package does not support platform `Linux`.
Because:
package:firebase_auth/firebase_auth.dart
that declares support for platforms:Android
,iOS
,Windows
,macOS
,Web
.
These issues are present but do not affect the score, because they may not originate in your package:
Package not compatible with platform Web
Because:
package:firebase_auth/firebase_auth.dart
that imports:dart:io
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:firebase_auth/firebase_auth.dart
that imports:dart:io
This package is not compatible with runtime wasm
, and will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
0/0 points: Swift Package Manager support
Package does not support the Swift Package Manager on macOS
It does not contain macos/firebase_auth/Package.swift
.
This package for iOS or macOS does not support the Swift Package Manager. It will not receive full points in a future version of the scoring model.
See https://docs.flutter.dev/to/spm for details.
50/50 points: code has no errors, warnings, lints, or formatting issues
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
firebase_auth_platform_interface |
^7.4.10 |
7.4.10 | 7.4.10 |
firebase_auth_web |
^5.13.5 |
5.13.5 | 5.13.5 |
firebase_core |
^3.8.1 |
3.9.0 | 3.9.0 |
firebase_core_platform_interface |
^5.3.1 |
5.4.0 | 5.4.0 |
flutter |
flutter |
0.0.0 | 0.0.0 |
meta |
^1.8.0 |
1.15.0 | 1.16.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
_flutterfire_internals |
- | 1.3.48 | 1.3.48 |
async |
- | 2.11.0 | 2.12.0 |
boolean_selector |
- | 2.1.1 | 2.1.2 |
characters |
- | 1.3.0 | 1.4.0 |
clock |
- | 1.1.1 | 1.1.2 |
collection |
- | 1.19.0 | 1.19.1 |
fake_async |
- | 1.3.1 | 1.3.2 |
firebase_core_web |
- | 2.19.0 | 2.19.0 |
flutter_test |
- | 0.0.0 | 0.0.0 |
flutter_web_plugins |
- | 0.0.0 | 0.0.0 |
http_parser |
- | 4.1.1 | 4.1.1 |
leak_tracker |
- | 10.0.7 | 10.0.8 |
leak_tracker_flutter_testing |
- | 3.0.8 | 3.0.9 |
leak_tracker_testing |
- | 3.0.1 | 3.0.1 |
matcher |
- | 0.12.16+1 | 0.12.17 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
path |
- | 1.9.0 | 1.9.1 |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 |
sky_engine |
- | 0.0.0 | 0.0.0 |
source_span |
- | 1.10.0 | 1.10.1 |
stack_trace |
- | 1.12.0 | 1.12.1 |
stream_channel |
- | 2.1.2 | 2.1.3 |
string_scanner |
- | 1.3.0 | 1.4.1 |
term_glyph |
- | 1.2.1 | 1.2.2 |
test_api |
- | 0.7.3 | 0.7.4 |
typed_data |
- | 1.4.0 | 1.4.0 |
vector_math |
- | 2.1.4 | 2.1.4 |
vm_service |
- | 14.3.0 | 15.0.0 |
web |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade
does not expose any static analysis error.
Analyzed with Pana 0.22.17
, Flutter 3.27.0
, Dart 3.6.0
.
Check the analysis log for details.