flutter_plugin_engagelab 1.3.3+520520
flutter_plugin_engagelab: ^1.3.3+520520 copied to clipboard
A new Flutter plugin.
We analyzed this package 8 days ago, and awarded it 130 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
The package description is too short.
Add more detail to the description field of pubspec.yaml. Use 50 to 180 characters to describe the package, what it does, and its target use case.
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
0/10 points: Use an OSI-approved license
No license was recognized.
Consider using an OSI-approved license in the LICENSE file to make it more accessible to the community.
10/10 points: 20% or more of the public API has dartdoc comments
42 out of 71 API elements (59.2 %) have documentation comments.
Some symbols that are missing documentation: flutter_plugin_engagelab, flutter_plugin_engagelab.EventHandler, flutter_plugin_engagelab.FlutterPluginEngagelab, flutter_plugin_engagelab.FlutterPluginEngagelab.FlutterPluginEngagelab.new, flutter_plugin_engagelab.FlutterPluginEngagelab.addEventHandler.
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_plugin_engagelab/flutter_plugin_engagelab.dartthat declares support for platforms:Android,iOS.
Package does not support platform `Linux`.
Because:
package:flutter_plugin_engagelab/flutter_plugin_engagelab.dartthat declares support for platforms:Android,iOS.
Package does not support platform `macOS`.
Because:
package:flutter_plugin_engagelab/flutter_plugin_engagelab.dartthat declares support for platforms:Android,iOS.
Package does not support platform `Web`.
Because:
package:flutter_plugin_engagelab/flutter_plugin_engagelab.dartthat declares support for platforms:Android,iOS.
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:flutter_plugin_engagelab/flutter_plugin_engagelab.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.dev/web/wasm for details.
0/0 points: Swift Package Manager support
Package does not support the Swift Package Manager on iOS
It does not contain ios/flutter_plugin_engagelab/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.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 137 issues. Showing the first 2:
INFO: Use the generic function type syntax in 'typedef's.
lib/flutter_plugin_engagelab.dart:7:25
╷
7 │ typedef Future<dynamic> EventHandler(Map<String, dynamic> event);
│ ^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/flutter_plugin_engagelab.dart
INFO: The constant name 'flutter_log' isn't a lowerCamelCase identifier.
lib/flutter_plugin_engagelab.dart:10:23
╷
10 │ static const String flutter_log = "| ENGAGELAB-PRIVATES-Flutter | ";
│ ^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/flutter_plugin_engagelab.dart
10/10 points: All of the package dependencies are supported in the latest version
No dependencies.
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
characters |
- | 1.4.0 | 1.4.1 | |
collection |
- | 1.19.1 | 1.19.1 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.16.0 | 1.17.0 | |
vector_math |
- | 2.2.0 | 2.2.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.23.0, Flutter 3.35.7, Dart 3.9.2.
Check the analysis log for details.