grpcgen 0.1.0+1 grpcgen: ^0.1.0+1 copied to clipboard
Command-line application for code generation for gRPC clients from gRPC Reflection.
We analyzed this package 2 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
0 out of 0 API elements (100.0 %) have documentation comments.
10/10 points: Package has an example
20/20 points: Supports 3 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Linux
-
✓ macOS
-
✓ Windows
These platforms are not supported:
Android
Cannot assign Android automatically to a binary only package.
iOS
Cannot assign iOS automatically to a binary only package.
Web
Cannot assign Web automatically to a binary only package.
0/0 points: WASM compatibility
Package not compatible with runtime wasm
Because:
package:grpcgen/src/grpc/generated/reflection.pbgrpc.dart
that imports:package:grpc/service_api.dart
that imports:package:grpc/src/server/service.dart
that imports:package:grpc/src/server/call.dart
that imports:package:grpc/src/shared/io_bits/io_bits.dart
that imports:package:grpc/src/shared/io_bits/io_bits_io.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 23 issues. Showing the first 2:
INFO: Dangling library doc comment.
lib/src/grpc/generated/google/protobuf/any.pb.dart:1:1
╷
1 │ ///
│ ^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/grpc/generated/google/protobuf/any.pb.dart
INFO: Dangling library doc comment.
lib/src/grpc/generated/google/protobuf/any.pbenum.dart:1:1
╷
1 │ ///
│ ^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/grpc/generated/google/protobuf/any.pbenum.dart
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
dart_style |
^2.2.4 |
2.3.7 | 2.3.7 |
fixnum |
^1.0.1 |
1.1.1 | 1.1.1 |
grpc |
^3.1.0 |
3.2.4 | 4.0.1 |
protobuf |
^2.1.0 |
2.1.0 | 3.1.0 |
recase |
^4.1.0 |
4.1.0 | 4.1.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
_fe_analyzer_shared |
- | 73.0.0 | 76.0.0 |
_macros |
- | 0.3.2 | 0.3.2 |
analyzer |
- | 6.8.0 | 6.11.0 |
archive |
- | 3.6.1 | 3.6.1 |
args |
- | 2.6.0 | 2.6.0 |
async |
- | 2.12.0 | 2.12.0 |
clock |
- | 1.1.2 | 1.1.2 |
collection |
- | 1.19.1 | 1.19.1 |
convert |
- | 3.1.2 | 3.1.2 |
crypto |
- | 3.0.6 | 3.0.6 |
file |
- | 7.0.1 | 7.0.1 |
glob |
- | 2.1.2 | 2.1.2 |
google_identity_services_web |
- | 0.3.1+5 | 0.3.1+5 |
googleapis_auth |
- | 1.6.0 | 1.6.0 |
http |
- | 1.2.2 | 1.2.2 |
http2 |
- | 2.3.0 | 2.3.0 |
http_parser |
- | 4.1.1 | 4.1.1 |
macros |
- | 0.1.2-main.4 | 0.1.3-main.0 |
meta |
- | 1.16.0 | 1.16.0 |
package_config |
- | 2.1.0 | 2.1.0 |
path |
- | 1.9.1 | 1.9.1 |
pub_semver |
- | 2.1.4 | 2.1.4 |
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 |
watcher |
- | 1.1.0 | 1.1.0 |
web |
- | 1.1.0 | 1.1.0 |
yaml |
- | 3.1.2 | 3.1.2 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^3.1.0` on grpc does not support the stable version `4.0.0`.
Try running dart pub upgrade --major-versions grpc
to update the constraint.
The constraint `^2.1.0` on protobuf does not support the stable version `3.0.0`.
Try running dart pub upgrade --major-versions protobuf
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.