consta_analytics 1.0.4
consta_analytics: ^1.0.4 copied to clipboard
SPA SDK for Flutter
We analyzed this package 18 days ago, and awarded it 125 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.
0/5 points: Provide a valid README.md
`README.md` contains too many non-ASCII characters.
The site uses English as its primary language. The content of README.md in your package should primarily contain characters used in English.
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: GPL-3.0.
10/10 points: 20% or more of the public API has dartdoc comments
59 out of 83 API elements (71.1 %) have documentation comments.
Some symbols that are missing documentation: event_manager, event_manager.EventManager, event_manager.EventManager.EventManager.new, event_manager.EventManager.boxName, event_manager.EventManager.getEvents.
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:consta_analytics/event_manager.dartthat declares support for platforms:Android,iOS.
Package does not support platform `Linux`.
Because:
package:consta_analytics/event_manager.dartthat declares support for platforms:Android,iOS.
Package does not support platform `macOS`.
Because:
package:consta_analytics/event_manager.dartthat declares support for platforms:Android,iOS.
Package does not support platform `Web`.
Because:
package:consta_analytics/event_manager.dartthat declares support for platforms:Android,iOS.
These issues are present but do not affect the score, because they may not originate in your package:
Package does not support platform `Android`.
Because:
package:consta_analytics/event_manager.dartthat imports:package:connectivity_plus/connectivity_plus.dartthat imports:package:connectivity_plus/src/connectivity_plus_linux.dartthat imports:package:nm/nm.dartthat declares support for platforms:Linux.
Package does not support platform `iOS`.
Because:
package:consta_analytics/event_manager.dartthat imports:package:connectivity_plus/connectivity_plus.dartthat imports:package:connectivity_plus/src/connectivity_plus_linux.dartthat imports:package:nm/nm.dartthat declares support for platforms:Linux.
0/0 points: Swift Package Manager support
Package does not support the Swift Package Manager on iOS
It does not contain ios/consta_analytics/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 8 issues. Showing the first 2:
INFO: 'SingletonFlutterWindow' is deprecated and shouldn't be used. Use FlutterView or PlatformDispatcher instead. Deprecated to prepare for the upcoming multi-window support. This feature was deprecated after v3.7.0-32.0.pre.
lib/spa_sdk.dart:79:16
╷
79 │ static final SingletonFlutterWindow _window = WidgetsBinding.instance.window;
│ ^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/spa_sdk.dart
INFO: 'window' is deprecated and shouldn't be used. Look up the current FlutterView from the context via View.of(context) or consult the PlatformDispatcher directly instead. Deprecated to prepare for the upcoming multi-window support. This feature was deprecated after v3.7.0-32.0.pre.
lib/spa_sdk.dart:79:73
╷
79 │ static final SingletonFlutterWindow _window = WidgetsBinding.instance.window;
│ ^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/spa_sdk.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
client_information |
^2.1.4 |
2.2.0 | 2.2.0 | |
connectivity_plus |
^6.0.3 |
6.1.5 | 7.0.0 | |
dio |
^5.5.0+1 |
5.9.0 | 5.9.0 | |
hive |
^2.2.3 |
2.2.3 | 2.2.3 | |
location |
^7.0.0 |
7.0.1 | 8.0.1 | |
uuid |
^4.4.2 |
4.5.2 | 4.5.2 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
args |
- | 2.7.0 | 2.7.0 | |
async |
- | 2.13.0 | 2.13.0 | |
characters |
- | 1.4.0 | 1.4.1 | |
collection |
- | 1.19.1 | 1.19.1 | |
connectivity_plus_platform_interface |
- | 2.0.1 | 2.0.1 | |
crypto |
- | 3.0.7 | 3.0.7 | |
dbus |
- | 0.7.11 | 0.7.11 | |
dio_web_adapter |
- | 2.1.1 | 2.1.1 | |
ffi |
- | 2.1.4 | 2.1.4 | |
fixnum |
- | 1.1.1 | 1.1.1 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
js |
- | 0.6.7 | 0.7.2 | Discontinued |
location_platform_interface |
- | 5.0.0 | 6.0.1 | |
location_web |
- | 5.0.4 | 6.0.1 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.17.0 | 1.17.0 | |
mime |
- | 2.0.0 | 2.0.0 | |
nm |
- | 0.5.0 | 0.5.0 | |
path |
- | 1.9.1 | 1.9.1 | |
petitparser |
- | 7.0.1 | 7.0.1 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
source_span |
- | 1.10.1 | 1.10.1 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
vector_math |
- | 2.2.0 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
xml |
- | 6.6.1 | 6.6.1 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
The constraint `^6.0.3` on connectivity_plus does not support the stable version `7.0.0`.
Try running dart pub upgrade --major-versions connectivity_plus to update the constraint.
The constraint `^7.0.0` on location does not support the stable version `8.0.0`.
Try running dart pub upgrade --major-versions location 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.3, Flutter 3.38.4, Dart 3.10.3.
Check the analysis log for details.