faker_dart 0.2.2 faker_dart: ^0.2.2 copied to clipboard
generate massive amounts of fake data in Dart & Flutter! A dart port of the famous faker.js
We analyzed this package 7 days ago, and awarded it 150 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
28 out of 29 API elements (96.6 %) have documentation comments.
Some symbols that are missing documentation: faker_dart
.
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
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 52 issues. Showing the first 2:
INFO: The file name 'af_ZA.dart' isn't a lower_case_with_underscores identifier.
To reproduce make sure you are using the lints_core and run dart analyze lib/src/locales/af_ZA.dart
INFO: The variable name 'af_ZA' isn't a lowerCamelCase identifier.
lib/src/locales/af_ZA.dart:1:22
╷
1 │ Map<String, dynamic> af_ZA = {
│ ^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/locales/af_ZA.dart
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
^1.18.0 |
1.19.1 | 1.19.1 |
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
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.