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: Apache-2.0.

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

Dependency resolution failed, unable to run dartdoc.

10/10 points: Package has an example

0/20 points: Platform support detection failed

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

• Running flutter pub outdated failed with the following output:

Note: test_api is pinned to version 0.7.7 by flutter_test from the flutter SDK.
See https://dart.cn/go/sdk-version-pinning for details.

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

• Could not run flutter pub outdated: flutter pub get failed:

OUT:
Resolving dependencies...
ERR:
Note: test_api is pinned to version 0.7.7 by flutter_test from the flutter SDK.
See https://dart.cn/go/sdk-version-pinning for details.


Because patrol depends on flutter_test from sdk which depends on test_api 0.7.7, test_api 0.7.7 is required.
So, because patrol depends on test_api >=0.4.0 <0.7.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Try upgrading your constraint on test_api: flutter pub add test_api:^0.7.7
[1 more lines]

10/10 points: Package supports latest stable Dart and Flutter SDKs

0/20 points: Compatible with dependency constraint lower bounds

flutter pub downgrade failed with:

OUT:
Resolving dependencies...
ERR:
Note: test_api is pinned to version 0.7.7 by flutter_test from the flutter SDK.
See https://dart.cn/go/sdk-version-pinning for details.


Because patrol depends on flutter_test from sdk which depends on test_api 0.7.7, test_api 0.7.7 is required.
So, because patrol depends on test_api >=0.4.0 <0.7.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Try upgrading your constraint on test_api: flutter pub add test_api:^0.7.7
[1 more lines]

Run flutter pub downgrade and then flutter 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.