validated 2.0.0 validated: ^2.0.0 copied to clipboard
The ultimate string validator for dart and flutter with over 40+ validators
We analyzed this package 7 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: BSD-2-Clause
.
10/10 points: 20% or more of the public API has dartdoc comments
57 out of 58 API elements (98.3 %) have documentation comments.
Some symbols that are missing documentation: validated
.
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.
30/50 points: code has no errors, warnings, lints, or formatting issues
Found 108 issues. Showing the first 2:
WARNING: The operand can't be 'null', so the condition is always 'true'.
lib/src/isBase64.dart:5:13
╷
5 │ if (input != null && input.length % 4 != 0 || _regExp.hasMatch(input)) {
│ ^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/isBase64.dart
WARNING: The operand can't be 'null', so the condition is always 'false'.
lib/src/isEmail.dart:9:13
╷
9 │ if (input == null) {
│ ^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/isEmail.dart
10/10 points: All of the package dependencies are supported in the latest version
No dependencies.
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.17
, Dart 3.6.0
.
Check the analysis log for details.