mojo_perception 2.0.1
mojo_perception: ^2.0.1 copied to clipboard
Mojo Perception Flutter API. Mojo Emotion AI Platform is a software framework to detect, understand and activate emotions.
We analyzed this package 2 days ago, and awarded it 140 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
Homepage URL doesn't exist.
At the time of the analysis https://docs.mojo.ai
was unreachable. Make sure that the website is reachable via HEAD
requests.
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
67 out of 149 API elements (45.0 %) have documentation comments.
Some symbols that are missing documentation: anchors
, anchors.Anchor
, anchors.Anchor.Anchor.new
, anchors.Anchor.h
, anchors.Anchor.w
.
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:mojo_perception/mojo_perception.dart
that imports:package:tflite_flutter/tflite_flutter.dart
that declares support for platforms:Android
,iOS
,Linux
.
Package does not support platform `Linux`.
Because:
package:mojo_perception/mojo_perception.dart
that imports:package:mojo_perception/services/image_converter.dart
that imports:package:camera/camera.dart
that declares support for platforms:Android
,iOS
,Web
.
Package does not support platform `macOS`.
Because:
package:mojo_perception/mojo_perception.dart
that imports:package:tflite_flutter/tflite_flutter.dart
that declares support for platforms:Android
,iOS
,Linux
.
Package does not support platform `Web`.
Because:
package:mojo_perception/mojo_perception.dart
that imports:package:tflite_flutter/tflite_flutter.dart
that declares support for platforms:Android
,iOS
,Linux
.
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:mojo_perception/mojo_perception.dart
that imports:package:tflite_flutter/tflite_flutter.dart
that imports:package:tflite_flutter/src/util/byte_conversion_utils.dart
that imports:package:tflite_flutter/src/bindings/types.dart
that imports:package:ffi/ffi.dart
that imports:package:ffi/src/utf16.dart
that imports:dart:ffi
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.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 3 issues. Showing the first 2:
INFO: Dangling library doc comment.
lib/mojo_perception.dart:1:1
╷
1 │ /// @license
│ ^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/mojo_perception.dart
INFO: The import of 'dart:typed_data' is unnecessary because all of the used elements are also provided by the import of 'package:flutter/services.dart'.
lib/mojo_perception.dart:26:8
╷
26 │ import 'dart:typed_data';
│ ^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/mojo_perception.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
camera |
^0.9.8 |
0.9.8+1 | 0.11.1 | |
image |
^3.1.3 |
3.3.0 | 4.5.4 | |
logging |
^1.0.2 |
1.3.0 | 1.3.0 | |
scidart |
^0.0.2-dev.6 |
0.0.2-dev.12 | 0.0.2-dev.12 | |
socket_io_client |
^2.0.0-beta.2 |
2.0.3+1 | 3.1.2 | |
tflite_flutter |
^0.9.0 |
0.9.1 | 0.11.0 | |
tflite_flutter_helper |
^0.3.1 |
0.3.1 | 0.3.1 | Discontinued |
Transitive dependencies
Package | Constraint | Compatible | Latest | Notes |
---|---|---|---|---|
archive |
- | 3.6.1 | 4.0.7 | |
async |
- | 2.13.0 | 2.13.0 | |
boolean_selector |
- | 2.1.2 | 2.1.2 | |
camera_android |
- | 0.9.8+3 | 0.10.10+3 | |
camera_avfoundation |
- | 0.9.20+1 | 0.9.20+1 | |
camera_platform_interface |
- | 2.10.0 | 2.10.0 | |
camera_web |
- | 0.2.1+6 | 0.3.5 | |
characters |
- | 1.4.0 | 1.4.1 | |
collection |
- | 1.19.1 | 1.19.1 | |
cross_file |
- | 0.3.4+2 | 0.3.4+2 | |
crypto |
- | 3.0.6 | 3.0.6 | |
ffi |
- | 1.2.1 | 2.1.4 | |
flutter_plugin_android_lifecycle |
- | 2.0.28 | 2.0.28 | |
js |
- | 0.6.7 | 0.7.2 | Discontinued |
matcher |
- | 0.12.17 | 0.12.17 | |
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 |
- | 2.0.15 | 2.1.5 | |
path_provider_android |
- | 2.2.17 | 2.2.17 | |
path_provider_foundation |
- | 2.4.1 | 2.4.1 | |
path_provider_linux |
- | 2.2.1 | 2.2.1 | |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 | |
path_provider_windows |
- | 2.0.7 | 2.3.0 | |
petitparser |
- | 6.1.0 | 7.0.0 | |
platform |
- | 3.1.6 | 3.1.6 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
quiver |
- | 3.2.2 | 3.2.2 | |
socket_io_common |
- | 2.0.3 | 3.1.1 | |
source_span |
- | 1.10.1 | 1.10.1 | |
stack_trace |
- | 1.12.1 | 1.12.1 | |
stream_channel |
- | 2.1.4 | 2.1.4 | |
stream_transform |
- | 2.1.1 | 2.1.1 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
test_api |
- | 0.7.6 | 0.7.6 | |
tuple |
- | 2.0.2 | 2.0.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
vector_math |
- | 2.1.4 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
win32 |
- | 2.6.1 | 5.14.0 | |
xdg_directories |
- | 1.1.0 | 1.1.0 | |
xml |
- | 6.5.0 | 6.6.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
Found 5 issues. Showing the first 2:
The constraint `^0.9.8` on camera does not support the stable version `0.10.0`.
Try running dart pub upgrade --major-versions camera
to update the constraint.
The constraint `^3.1.3` on image does not support the stable version `4.0.0`.
Try running dart pub upgrade --major-versions image
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.22.21
, Flutter 3.32.4
, Dart 3.8.1
.
Check the analysis log for details.