hermez_sdk 1.0.0+2 hermez_sdk: ^1.0.0+2 copied to clipboard
Hermez Flutter SDK (https://hermez.io). This plugin provides a cross-platform (iOS, Android) to communicate with the Hermez Network.
We analyzed this package 3 days ago, and awarded it 70 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
Documentation URL doesn't exist.
At the time of the analysis https://docs.hermez.io/
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: GPL-3.0
.
0/10 points: 20% or more of the public API has dartdoc comments
93 out of 652 API elements (14.3 %) have documentation comments.
Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API. Document at least 20% of the public API elements.
To highlight public API members missing documentation consider enabling the public_member_api_docs
lint.
Some symbols that are missing documentation: account
, account.Account
, account.Account.Account
, account.Account.Account.fromJson
, account.Account.accountIndex
.
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:hermez_sdk/hermez_sdk.dart
that declares support for platforms:Android
,iOS
.
Package does not support platform `Linux`.
Because:
package:hermez_sdk/hermez_sdk.dart
that declares support for platforms:Android
,iOS
.
Package does not support platform `macOS`.
Because:
package:hermez_sdk/hermez_sdk.dart
that declares support for platforms:Android
,iOS
.
Package does not support platform `Web`.
Because:
package:hermez_sdk/hermez_sdk.dart
that declares support for platforms:Android
,iOS
.
0/0 points: WASM compatibility
Unable to detect compatibility with runtime wasm
, and this package will not be rewarded full points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 82 issues. Showing the first 2:
ERROR: Fields in struct classes can't have the type 'Pointer
lib/utils/structs.dart:48:3
╷
48 │ Pointer<Point>? r_b8;
│ ^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/utils/structs.dart
ERROR: Fields of 'Struct' and 'Union' subclasses must be marked external.
lib/utils/structs.dart:48:19
╷
48 │ Pointer<Point>? r_b8;
│ ^^^^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/utils/structs.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
bip39 |
^1.0.6 |
1.0.6 | 1.0.6 |
ffi |
^1.1.2 |
1.2.1 | 2.1.3 |
flutter |
flutter |
0.0.0 | 0.0.0 |
hex |
^0.2.0 |
0.2.0 | 0.2.0 |
http |
^0.13.3 |
0.13.6 | 1.2.2 |
provider |
^5.0.0 |
5.0.0 | 6.1.2 |
shared_preferences |
^2.0.6 |
2.3.3 | 2.3.3 |
web3dart |
^2.1.3 |
2.6.1 | 2.7.3 |
web_socket_channel |
^2.1.0 |
2.4.5 | 3.0.1 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.12.0 | 2.12.0 |
characters |
- | 1.3.0 | 1.3.1 |
collection |
- | 1.18.0 | 1.19.1 |
convert |
- | 3.1.2 | 3.1.2 |
crypto |
- | 3.0.6 | 3.0.6 |
eip1559 |
- | 0.6.1 | 0.6.2 |
eip55 |
- | 1.0.2 | 1.0.2 |
file |
- | 7.0.1 | 7.0.1 |
flutter_web_plugins |
- | 0.0.0 | 0.0.0 |
http_parser |
- | 4.0.2 | 4.1.1 |
js |
- | 0.7.1 | 0.7.1 |
json_rpc_2 |
- | 3.0.3 | 3.0.3 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
meta |
- | 1.15.0 | 1.16.0 |
nested |
- | 1.0.0 | 1.0.0 |
path |
- | 1.9.1 | 1.9.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 |
platform |
- | 3.1.6 | 3.1.6 |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 |
pointycastle |
- | 3.9.1 | 3.9.1 |
sec |
- | 1.1.0 | 1.1.0 |
shared_preferences_android |
- | 2.3.3 | 2.3.3 |
shared_preferences_foundation |
- | 2.5.3 | 2.5.3 |
shared_preferences_linux |
- | 2.4.1 | 2.4.1 |
shared_preferences_platform_interface |
- | 2.4.1 | 2.4.1 |
shared_preferences_web |
- | 2.4.2 | 2.4.2 |
shared_preferences_windows |
- | 2.4.1 | 2.4.1 |
sky_engine |
- | 0.0.99 | 0.0.99 |
source_span |
- | 1.10.0 | 1.10.0 |
stack_trace |
- | 1.12.0 | 1.12.0 |
stream_channel |
- | 2.1.2 | 2.1.2 |
stream_transform |
- | 2.1.0 | 2.1.0 |
string_scanner |
- | 1.4.0 | 1.4.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.4.0 | 1.4.0 |
uuid |
- | 3.0.7 | 4.5.1 |
vector_math |
- | 2.1.4 | 2.1.4 |
wallet |
- | 0.0.13 | 0.0.13 |
web |
- | 0.5.1 | 1.1.0 |
win32 |
- | 2.6.1 | 5.8.0 |
xdg_directories |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
Found 4 issues. Showing the first 2:
The constraint `^1.1.2` on ffi does not support the stable version `2.0.0`.
Try running dart pub upgrade --major-versions ffi
to update the constraint.
The constraint `^0.13.3` on http does not support the stable version `1.0.0`.
Try running dart pub upgrade --major-versions http
to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 10 errors:
INVALID_FIELD_TYPE_IN_STRUCT
-lib/utils/structs.dart:48:3
- Fields in struct classes can't have the type 'PointerFIELD_MUST_BE_EXTERNAL_IN_STRUCT
-lib/utils/structs.dart:48:19
- Fields of 'Struct' and 'Union' subclasses must be marked external.INVALID_FIELD_TYPE_IN_STRUCT
-lib/utils/structs.dart:50:3
- Fields in struct classes can't have the type 'Pointer
Run flutter pub downgrade
and then flutter analyze
to reproduce the above problem.
You may run dart pub upgrade --tighten
to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.22.15
, Flutter 3.24.4
, Dart 3.5.4
.
Check the analysis log for details.