acme_client 1.3.0 acme_client: ^1.3.0 copied to clipboard
ACME client which allows you to obtain a HTTPS Certificate from any ACME CA such as Lets Encrypt.
We analyzed this package 6 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: MIT
.
10/10 points: 20% or more of the public API has dartdoc comments
25 out of 125 API elements (20.0 %) have documentation comments.
Some symbols that are missing documentation: acme_client
, acme_client.Account
, acme_client.Account.Account
, acme_client.Account.Account.fromJson
, acme_client.Account.accountURL
.
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:acme_client/acme_client.dart
that imports:package:acme_client/src/acme_util.dart
that imports:package:basic_utils/basic_utils.dart
that imports:package:basic_utils/src/Asn1Utils.dart
that imports:package:basic_utils/src/CryptoUtils.dart
that imports:package:basic_utils/src/StringUtils.dart
that imports:dart:io
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:acme_client/acme_client.dart
that imports:package:acme_client/src/acme_util.dart
that imports:package:basic_utils/basic_utils.dart
that imports:package:basic_utils/src/Asn1Utils.dart
that imports:package:basic_utils/src/CryptoUtils.dart
that imports:package:basic_utils/src/StringUtils.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.
50/50 points: code has no errors, warnings, lints, or formatting issues
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
basic_utils |
^5.5.4 |
5.7.0 | 5.7.0 |
dio |
^5.0.0 |
5.7.0 | 5.7.0 |
jose |
^0.3.2 |
0.3.4 | 0.3.4 |
json_annotation |
^4.1.0 |
4.9.0 | 4.9.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
asn1lib |
- | 1.5.8 | 1.5.8 |
async |
- | 2.12.0 | 2.12.0 |
boolean_selector |
- | 2.1.2 | 2.1.2 |
collection |
- | 1.19.1 | 1.19.1 |
convert |
- | 3.1.2 | 3.1.2 |
crypto_keys |
- | 0.3.0+1 | 0.3.0+1 |
dio_web_adapter |
- | 2.0.0 | 2.0.0 |
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 |
matcher |
- | 0.12.17 | 0.12.17 |
meta |
- | 1.16.0 | 1.16.0 |
path |
- | 1.9.1 | 1.9.1 |
pointycastle |
- | 3.9.1 | 3.9.1 |
quiver |
- | 3.2.2 | 3.2.2 |
source_span |
- | 1.10.1 | 1.10.1 |
stack_trace |
- | 1.12.1 | 1.12.1 |
stream_channel |
- | 2.1.3 | 2.1.3 |
string_scanner |
- | 1.4.1 | 1.4.1 |
term_glyph |
- | 1.2.2 | 1.2.2 |
test_api |
- | 0.7.4 | 0.7.4 |
typed_data |
- | 1.4.0 | 1.4.0 |
web |
- | 1.1.0 | 1.1.0 |
x509 |
- | 0.2.4+3 | 0.2.4+3 |
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
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 11 errors:
NON_TYPE_IN_CATCH_CLAUSE
-lib/src/acme_client.dart:125:10
- The name 'DioException' isn't a type and can't be used in an on-catch clause.NON_TYPE_IN_CATCH_CLAUSE
-lib/src/acme_client.dart:151:10
- The name 'DioException' isn't a type and can't be used in an on-catch clause.NON_TYPE_IN_CATCH_CLAUSE
-lib/src/acme_client.dart:174:10
- The name 'DioException' isn't a type and can't be used in an on-catch clause.
Run dart pub downgrade
and then dart analyze
to reproduce the above problem.
You may run dart pub upgrade --tighten
to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.22.17
, Dart 3.6.0
.
Check the analysis log for details.