buildbucket 1.0.12
buildbucket: ^1.0.12 copied to clipboard

Published 9 months ago

[analysis issue]

→

Metadata

LUCI Buildbucket library. Protos and utilities to communicate with LUCI buildbucket service.

More...

likes

70/ 160

pub points

1.38k

downloads

We analyzed this package 6 hours ago, and awarded it 70 pub points (of a possible 160):

Follow Dart file conventions

30 / 30

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-3-Clause.

Provide documentation

10 / 20

10/10 points: 20% or more of the public API has dartdoc comments

3573 out of 5751 API elements (62.1 %) have documentation comments.

Some symbols that are missing documentation: buildbucket, buildbucket.Any.Any.fromBuffer, buildbucket.Any.Any.fromJson, buildbucket.Any.check, buildbucket.Any.clearTypeUrl.

0/10 points: Package has an example

No example found.

See package layout guidelines on how to add an example.

Platform support

20 / 20

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

Unable to detect compatibility with runtime wasm, and this package will not be rewarded full points in a future version of the scoring model.

See https://dart.dev/web/wasm for details.

Pass static analysis

0 / 50

0/50 points: code has no errors, warnings, lints, or formatting issues

Found 14 issues. Showing the first 2:

ERROR: Target of URI hasn't been generated: 'test_variant.pb.dart'.

lib/src/generated/go.chromium.org/luci/resultdb/proto/v1/resultdb.pb.dart:23:8

   ╷
23 │ import 'test_variant.pb.dart' as $6;
   │        ^^^^^^^^^^^^^^^^^^^^^^
   ╵

To reproduce make sure you are using the lints_core and run dart analyze lib/src/generated/go.chromium.org/luci/resultdb/proto/v1/resultdb.pb.dart

INFO: Dangling library doc comment.

lib/src/generated/go.chromium.org/luci/buildbucket/proto/build.pbserver.dart:1:1

  ╷
1 │ ///
  │ ^^^
  ╵

To reproduce make sure you are using the lints_core and run dart analyze lib/src/generated/go.chromium.org/luci/buildbucket/proto/build.pbserver.dart

Support up-to-date dependencies

10 / 40

0/10 points: All of the package dependencies are supported in the latest version

Package	Constraint	Compatible	Latest
`fixnum`	`1.1.0`	1.1.0	1.1.1
`grpc`	`3.2.4`	3.2.4	4.0.1
`protobuf`	`3.1.0`	3.1.0	3.1.0
`protoc_plugin`	`21.1.2`	21.1.2	21.1.2

Transitive dependencies

Package	Constraint	Compatible	Latest
`archive`	-	3.6.1	4.0.2
`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
`crypto`	-	3.0.6	3.0.6
`google_identity_services_web`	-	0.3.3	0.3.3
`googleapis_auth`	-	1.6.0	1.6.0
`http`	-	1.2.2	1.2.2
`http2`	-	2.3.1	2.3.1
`http_parser`	-	4.1.2	4.1.2
`meta`	-	1.16.0	1.16.0
`path`	-	1.9.1	1.9.1
`source_span`	-	1.10.1	1.10.1
`string_scanner`	-	1.4.1	1.4.1
`term_glyph`	-	1.2.2	1.2.2
`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 `1.1.0` on fixnum does not support the stable version `1.1.1`.

Try running dart pub upgrade --major-versions fixnum to update the constraint.

The constraint `3.2.4` on grpc does not support the stable version `4.0.0`.

Try running dart pub upgrade --major-versions grpc to update the constraint.

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 1 error:

URI_HAS_NOT_BEEN_GENERATED - lib/src/generated/go.chromium.org/luci/resultdb/proto/v1/resultdb.pb.dart:23:8 - Target of URI hasn't been generated: 'test_variant.pb.dart'.

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.