dart_native_annoy 0.1.0 dart_native_annoy: ^0.1.0 copied to clipboard
A dart binding to native annoy library to serve pre-built Annoy index.
We analyzed this package 4 days ago, and awarded it 120 pub points (of a possible 140):
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
19 out of 48 API elements (39.6 %) have documentation comments.
Some symbols that are missing documentation: annoy
, annoy.AnnoyIndex.dimension
, annoy.AnnoyIndex.size
, annoy.AnnoyIndex.type
, annoy.AnnoyIndexSearchResult
.
10/10 points: Package has an example
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
- ✓ Android
- ✓ iOS
- ✓ Windows
- ✓ Linux
- ✓ macOS
These platforms are not supported:
Package not compatible with platform Web
Because:
package:dart_native_annoy/annoy.dart
that imports:package:dart_native_annoy/src/annoy_index.dart
that imports:package:dart_native_annoy/utils/native_array_utils.dart
that imports:package:ffi/ffi.dart
that imports:package:ffi/src/utf16.dart
that imports:dart:ffi
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: The part-of directive uses a library name.
lib/src/index_type.dart:1:1
╷
1 │ part of annoy;
│ ^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/index_type.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
ffi |
^1.0.0 |
1.2.1 | 2.1.2 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^1.0.0` on ffi does not support the stable version `2.0.0`.
Try running dart pub upgrade --major-versions ffi
to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.4
.
Check the analysis log for details.