intasend_flutter 0.0.2 intasend_flutter: ^0.0.2 copied to clipboard
Flutter plugin for IntaSend payments integration. Collect M-Pesa, and card payments.
We analyzed this package 8 days ago, and awarded it 110 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: AGPL-3.0
.
0/10 points: 20% or more of the public API has dartdoc comments
5 out of 48 API elements (10.4 %) 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: api
, api.IntaSendAPI
, api.IntaSendAPI.IntaSendAPI
, api.IntaSendAPI.createCheckout
, api.IntaSendAPI.sendSTKPushRequest
.
10/10 points: Package has an example
0/20 points: Supports 0 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
These platforms are not supported:
Package does not support platform `Android`.
Because:
package:intasend_flutter/intasend_flutter.dart
that declares support for platforms: .
Package does not support platform `iOS`.
Because:
package:intasend_flutter/intasend_flutter.dart
that declares support for platforms: .
Package does not support platform `Windows`.
Because:
package:intasend_flutter/intasend_flutter.dart
that declares support for platforms: .
Package does not support platform `Linux`.
Because:
package:intasend_flutter/intasend_flutter.dart
that declares support for platforms: .
Package does not support platform `macOS`.
Because:
package:intasend_flutter/intasend_flutter.dart
that declares support for platforms: .
Package does not support platform `Web`.
Because:
package:intasend_flutter/intasend_flutter.dart
that declares support for platforms: .
0/0 points: WASM compatibility
This package is compatible with runtime wasm
, and will be rewarded additional 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
Found 3 issues. Showing the first 2:
INFO: Using a colon as the separator before a default value is deprecated and will not be supported in language version 3.0 and later.
lib/intasend_flutter.dart:14:17
╷
14 │ {bool test: false,
│ ^
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/intasend_flutter.dart
lib/intasend_flutter_method_channel.dart doesn't match the Dart formatter.
To format your files run: dart format .
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
flutter |
flutter |
0.0.0 | 0.0.0 |
flutter_webview_plugin |
^0.4.0 |
0.4.0 | 0.4.0 |
http |
^0.13.4 |
0.13.6 | 1.2.2 |
plugin_platform_interface |
^2.0.2 |
2.1.8 | 2.1.8 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
- | 2.11.0 | 2.11.0 |
characters |
- | 1.3.0 | 1.3.0 |
collection |
- | 1.18.0 | 1.19.0 |
http_parser |
- | 4.0.2 | 4.1.0 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
meta |
- | 1.15.0 | 1.16.0 |
path |
- | 1.9.0 | 1.9.0 |
sky_engine |
- | 0.0.99 | 0.0.99 |
source_span |
- | 1.10.0 | 1.10.0 |
string_scanner |
- | 1.3.0 | 1.3.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.3.2 | 1.3.2 |
vector_math |
- | 2.1.4 | 2.1.4 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^0.13.4` 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
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade
does not expose any static analysis error.
Analyzed with Pana 0.22.12
, Flutter 3.24.3
, Dart 3.5.3
.
Check the analysis log for details.