flutter_rust_bridge 1.82.6 flutter_rust_bridge: ^1.82.6 copied to clipboard
High-level memory-safe binding generator for Flutter/Dart <-> Rust
We analyzed this package 4 days 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
353 out of 960 API elements (36.8 %) have documentation comments.
Some symbols that are missing documentation: flutter_rust_bridge
, flutter_rust_bridge.DartApiDl
, flutter_rust_bridge.DartApiDl.DartApiDl
, flutter_rust_bridge.DartApiDl.initApi
, flutter_rust_bridge.DropFnType
.
10/10 points: Package has an example
20/20 points: Supports 6 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ Linux
-
✓ macOS
-
✓ Web
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:flutter_rust_bridge/flutter_rust_bridge.dart
that imports:package:flutter_rust_bridge/src/load.dart
that imports:package:flutter_rust_bridge/src/load/load.io.dart
that 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.
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: 'elementAt' is deprecated and shouldn't be used. Use operator + instead.
lib/src/ffi/dart_cobject.dart:28:32
╷
28 │ while (value.as_string.elementAt(len).value != 0) {
│ ^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/ffi/dart_cobject.dart
INFO: 'elementAt' is deprecated and shouldn't be used. Use operator + instead.
lib/src/ffi/dart_cobject.dart:35:42
╷
35 │ (i) => value.as_array.values.elementAt(i).value.ref.intoDart());
│ ^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/ffi/dart_cobject.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
args |
^2.3.1 |
2.6.0 | 2.6.0 |
build_cli_annotations |
^2.1.0 |
2.1.0 | 2.1.0 |
js |
^0.6.4 |
0.6.7 | 0.7.1 |
meta |
^1.3.0 |
1.16.0 | 1.16.0 |
path |
^1.8.1 |
1.9.1 | 1.9.1 |
puppeteer |
^3.1.1 |
3.15.0 | 3.15.0 |
shelf |
^1.3.2 |
1.4.2 | 1.4.2 |
shelf_static |
^1.1.1 |
1.1.3 | 1.1.3 |
shelf_web_socket |
^1.0.2 |
1.0.4 | 2.0.0 |
tuple |
^2.0.1 |
2.0.2 | 2.0.2 |
uuid |
^4.1.0 |
4.5.1 | 4.5.1 |
web_socket_channel |
^2.2.0 |
2.4.5 | 3.0.1 |
yaml |
^3.1.1 |
3.1.2 | 3.1.2 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
archive |
- | 3.6.1 | 3.6.1 |
async |
- | 2.12.0 | 2.12.0 |
collection |
- | 1.19.1 | 1.19.1 |
convert |
- | 3.1.2 | 3.1.2 |
crypto |
- | 3.0.6 | 3.0.6 |
fixnum |
- | 1.1.1 | 1.1.1 |
http |
- | 1.2.2 | 1.2.2 |
http_parser |
- | 4.1.1 | 4.1.1 |
logging |
- | 1.3.0 | 1.3.0 |
mime |
- | 2.0.0 | 2.0.0 |
petitparser |
- | 6.0.2 | 6.0.2 |
pool |
- | 1.5.1 | 1.5.1 |
source_span |
- | 1.10.0 | 1.10.0 |
sprintf |
- | 7.0.0 | 7.0.0 |
stack_trace |
- | 1.12.0 | 1.12.0 |
stream_channel |
- | 2.1.2 | 2.1.2 |
string_scanner |
- | 1.4.0 | 1.4.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.4.0 | 1.4.0 |
web |
- | 0.5.1 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
Found 3 issues. Showing the first 2:
The constraint `^0.6.4` on js does not support the stable version `0.7.0`.
Try running dart pub upgrade --major-versions js
to update the constraint.
The constraint `^1.0.2` on shelf_web_socket does not support the stable version `2.0.0`.
Try running dart pub upgrade --major-versions shelf_web_socket
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.15
, Dart 3.5.4
.
Check the analysis log for details.