emvqrjson 1.1.0 emvqrjson: ^1.1.0 copied to clipboard
read or write emvqrcode
We analyzed this package 9 days ago, and awarded it 110 pub points (of a possible 140):
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 60 to 180 characters to describe the package, what it does, and its target use case.
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
.
0/10 points: 20% or more of the public API has dartdoc comments
0 out of 4 API elements (0.0 %) 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.
Some symbols that are missing documentation: emvqrjson
, emvqrjson.isEmvQrCode
, emvqrjson.readEmvQrCodeToJson
, emvqrjson.writeJsonToEmvQrCode
.
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
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 3 issues. Showing the first 2:
lib/src/read_emvqr_json.dart doesn't match the Dart formatter.
To format your files run: dart format .
lib/src/verify_emvqr_json.dart doesn't match the Dart formatter.
To format your files run: dart format .
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
crclib |
^3.0.0 |
3.0.0 | 3.0.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
meta |
- | 1.14.0 | 1.14.0 |
tuple |
- | 2.0.2 | 2.0.2 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.3
.
Check the analysis log for details.