enough_mail 2.1.6 enough_mail: ^2.1.6 copied to clipboard
IMAP, POP3 and SMTP for email developers. Choose between a low level and a high level API for mailing. Parse and generate MIME messages. Discover email settings.
We analyzed this package 6 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: MPL-2.0
.
10/10 points: 20% or more of the public API has dartdoc comments
1488 out of 1488 API elements (100.0 %) have documentation comments.
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:enough_mail/enough_mail.dart
that imports:package:enough_mail/smtp.dart
that imports:package:enough_mail/src/smtp/smtp_exception.dart
that imports:package:enough_mail/src/smtp/smtp_client.dart
that imports:package:enough_mail/src/private/util/client_base.dart
that imports:dart:io
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:enough_mail/enough_mail.dart
that imports:package:enough_mail/smtp.dart
that imports:package:enough_mail/src/smtp/smtp_exception.dart
that imports:package:enough_mail/src/smtp/smtp_client.dart
that imports:package:enough_mail/src/private/util/client_base.dart
that imports:dart:io
This package is not compatible with runtime wasm
, and will not be rewarded full 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 10 issues. Showing the first 2:
INFO: Dangling library doc comment.
lib/codecs.dart:1:1
╷
1 │ /// Email codec classes
│ ^^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/codecs.dart
INFO: Dangling library doc comment.
lib/discover.dart:1:1
╷
1 │ /// Discovers email settings based on an email address.
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/discover.dart
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
basic_utils |
^5.6.1 |
5.7.0 | 5.7.0 |
collection |
^1.16.0 |
1.19.1 | 1.19.1 |
crypto |
^3.0.0 |
3.0.6 | 3.0.6 |
encrypt |
^5.0.0 |
5.0.3 | 5.0.3 |
enough_convert |
^1.5.0 |
1.6.0 | 1.6.0 |
event_bus |
^2.0.0 |
2.0.1 | 2.0.1 |
intl |
^0.19.0 |
0.19.0 | 0.20.0 |
json_annotation |
^4.8.0 |
4.9.0 | 4.9.0 |
pointycastle |
^3.6.0 |
3.9.1 | 3.9.1 |
synchronized |
^3.1.0 |
3.3.0+3 | 3.3.0+3 |
xml |
>=6.0.0 <7.0.0 |
6.5.0 | 6.5.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
args |
- | 2.6.0 | 2.6.0 |
asn1lib |
- | 1.5.8 | 1.5.8 |
async |
- | 2.12.0 | 2.12.0 |
clock |
- | 1.1.2 | 1.1.2 |
convert |
- | 3.1.2 | 3.1.2 |
http |
- | 1.2.2 | 1.2.2 |
http_parser |
- | 4.1.1 | 4.1.1 |
js |
- | 0.7.1 | 0.7.1 |
logging |
- | 1.3.0 | 1.3.0 |
meta |
- | 1.16.0 | 1.16.0 |
path |
- | 1.9.1 | 1.9.1 |
petitparser |
- | 6.0.2 | 6.0.2 |
source_span |
- | 1.10.0 | 1.10.0 |
string_scanner |
- | 1.4.0 | 1.4.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
typed_data |
- | 1.4.0 | 1.4.0 |
web |
- | 1.1.0 | 1.1.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^0.19.0` on intl does not support the stable version `0.20.0`, that was published 0 days ago.
When intl is 30 days old, this package will no longer be awarded points in this category.
Try running dart pub upgrade --major-versions intl
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.15
, Dart 3.5.4
.
Check the analysis log for details.