flutter_liveness_check 1.0.8
flutter_liveness_check: ^1.0.8 copied to clipboard
A comprehensive Flutter package for face liveness detection with ML Kit.
We analyzed this package 14 hours ago, and awarded it 140 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: MIT.
10/10 points: 20% or more of the public API has dartdoc comments
180 out of 192 API elements (93.8 %) have documentation comments.
Some symbols that are missing documentation: dashed_circle_painter, device_helper, enhence_light_checker, enhence_light_checker.BlurDetectionResult.BlurDetectionResult.new, enhence_light_checker.EnhancedQualityDetector.EnhancedQualityDetector.new.
10/10 points: Package has an example
20/20 points: Supports 2 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
These platforms are not supported:
Package does not support platform `Windows`.
Because:
package:flutter_liveness_check/flutter_liveness_check.dartthat imports:package:flutter_liveness_check/enhence_light_checker.dartthat imports:package:google_mlkit_face_detection/google_mlkit_face_detection.dartthat declares support for platforms:Android,iOS.
Package does not support platform `Linux`.
Because:
package:flutter_liveness_check/flutter_liveness_check.dartthat imports:package:flutter_liveness_check/enhence_light_checker.dartthat imports:package:google_mlkit_face_detection/google_mlkit_face_detection.dartthat declares support for platforms:Android,iOS.
Package does not support platform `macOS`.
Because:
package:flutter_liveness_check/flutter_liveness_check.dartthat imports:package:flutter_liveness_check/enhence_light_checker.dartthat imports:package:google_mlkit_face_detection/google_mlkit_face_detection.dartthat declares support for platforms:Android,iOS.
Package does not support platform `Web`.
Because:
package:flutter_liveness_check/flutter_liveness_check.dartthat imports:package:flutter_liveness_check/enhence_light_checker.dartthat imports:package:google_mlkit_face_detection/google_mlkit_face_detection.dartthat declares support for platforms:Android,iOS.
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:flutter_liveness_check/flutter_liveness_check.dartthat imports:package:flutter_liveness_check/enhence_light_checker.dartthat imports:package:google_mlkit_face_detection/google_mlkit_face_detection.dartthat imports:package:google_mlkit_face_detection/src/face_detector.dartthat imports:package:google_mlkit_commons/google_mlkit_commons.dartthat imports:package:google_mlkit_commons/src/input_image.dartthat 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.cn/web/wasm for details.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 4 issues. Showing the first 2:
/tmp/pana_JAFSIO/lib/enhence_light_checker.dart doesn't match the Dart formatter.
To format your files run: dart format .
/tmp/pana_JAFSIO/lib/liveness_check_errors.dart doesn't match the Dart formatter.
To format your files run: dart format .
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
camera |
^0.10.5+5 |
0.10.6 | 0.11.3 | |
device_info_plus |
^9.1.1 |
9.1.2 | 12.2.0 | |
google_mlkit_face_detection |
^0.10.0 |
0.10.1 | 0.13.1 | |
image |
^4.0.17 |
4.5.4 | 4.5.4 | |
path_provider |
^2.1.1 |
2.1.5 | 2.1.5 | |
permission_handler |
^11.0.1 |
11.4.0 | 12.0.1 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
archive |
- | 4.0.7 | 4.0.7 | |
camera_android |
- | 0.10.10+11 | 0.10.10+11 | |
camera_avfoundation |
- | 0.9.22+4 | 0.9.22+4 | |
camera_platform_interface |
- | 2.12.0 | 2.12.0 | |
camera_web |
- | 0.3.5 | 0.3.5 | |
characters |
- | 1.4.0 | 1.4.1 | |
collection |
- | 1.19.1 | 1.19.1 | |
cross_file |
- | 0.3.5 | 0.3.5 | |
crypto |
- | 3.0.7 | 3.0.7 | |
device_info_plus_platform_interface |
- | 7.0.3 | 7.0.3 | |
ffi |
- | 2.1.4 | 2.1.4 | |
file |
- | 7.0.1 | 7.0.1 | |
flutter_plugin_android_lifecycle |
- | 2.0.32 | 2.0.32 | |
google_mlkit_commons |
- | 0.7.1 | 0.11.0 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.16.0 | 1.17.0 | |
path |
- | 1.9.1 | 1.9.1 | |
path_provider_android |
- | 2.2.20 | 2.2.20 | |
path_provider_foundation |
- | 2.4.3 | 2.4.3 | |
path_provider_linux |
- | 2.2.1 | 2.2.1 | |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 | |
path_provider_windows |
- | 2.3.0 | 2.3.0 | |
permission_handler_android |
- | 12.1.0 | 13.0.1 | |
permission_handler_apple |
- | 9.4.7 | 9.4.7 | |
permission_handler_html |
- | 0.1.3+5 | 0.1.3+5 | |
permission_handler_platform_interface |
- | 4.3.0 | 4.3.0 | |
permission_handler_windows |
- | 0.2.1 | 0.2.1 | |
petitparser |
- | 7.0.1 | 7.0.1 | |
platform |
- | 3.1.6 | 3.1.6 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
posix |
- | 6.0.3 | 6.0.3 | |
stream_transform |
- | 2.1.1 | 2.1.1 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
vector_math |
- | 2.2.0 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
win32 |
- | 5.15.0 | 5.15.0 | |
win32_registry |
- | 1.1.5 | 2.1.0 | |
xdg_directories |
- | 1.1.0 | 1.1.0 | |
xml |
- | 6.6.1 | 6.6.1 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
Found 4 issues. Showing the first 2:
The constraint `^0.10.5+5` on camera does not support the stable version `0.11.0`.
Try running dart pub upgrade --major-versions camera to update the constraint.
The constraint `^9.1.1` on device_info_plus does not support the stable version `10.0.0`.
Try running dart pub upgrade --major-versions device_info_plus to update the constraint.
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.23.0, Flutter 3.35.7, Dart 3.9.2.
Check the analysis log for details.