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 and has no issues with screenshots

0/20 points: Platform support detection failed

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.cn/web/wasm for details.

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

• Running dart pub outdated failed with the following output:

Because no versions of macros match >=0.1.0 <0.1.1-main.0 and macros >=0.1.1-main.0 <0.1.2-main.0 depends on _macros 0.2.0 from sdk, macros >=0.1.0 <0.1.2-main.0 requires _macros 0.2.0 from sdk.
And because macros >=0.1.2-main.0 <0.1.2-main.2 depends on _macros 0.3.0 from sdk and macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk, macros >=0.1.0 <0.1.2-main.4 requires _macros 0.2.0 or 0.3.0 or 0.3.1 from sdk.

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

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

OUT:
Resolving dependencies...
ERR:
Because no versions of macros match >=0.1.0 <0.1.1-main.0 and macros >=0.1.1-main.0 <0.1.2-main.0 depends on _macros 0.2.0 from sdk, macros >=0.1.0 <0.1.2-main.0 requires _macros 0.2.0 from sdk.
And because macros >=0.1.2-main.0 <0.1.2-main.2 depends on _macros 0.3.0 from sdk and macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk, macros >=0.1.0 <0.1.2-main.4 requires [...]
And because macros >=0.1.2-main.4 <0.1.3-main.0 depends on _macros 0.3.2 from sdk and macros >=0.1.3-main.0 depends on _macros 0.3.3 from sdk, macros >=0.1.0 requires _macros 0.2.0 or 0.3.0 or 0.[...]
So, because _macros from sdk doesn't exist (could not find package _macros in the Dart SDK) and classy depends on macros ^0.1.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on macros: dart pub add macros:^0.0.1

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

0/20 points: Compatible with dependency constraint lower bounds

dart pub downgrade failed with:

OUT:
Resolving dependencies...
ERR:
Because no versions of macros match >=0.1.0 <0.1.1-main.0 and macros >=0.1.3-main.0 depends on _macros 0.3.3 from sdk, macros >=0.1.0 <0.1.1-main.0 or >=0.1.3-main.0 requires _macros 0.3.3 from sdk.
And because macros >=0.1.2-main.4 <0.1.3-main.0 depends on _macros 0.3.2 from sdk and macros >=0.1.2-main.2 <0.1.2-main.4 depends on _macros 0.3.1 from sdk, macros >=0.1.0 <0.1.1-main.0 or >=0.1.[...]
And because macros >=0.1.2-main.0 <0.1.2-main.2 depends on _macros 0.3.0 from sdk and macros >=0.1.1-main.0 <0.1.2-main.0 depends on _macros 0.2.0 from sdk, macros >=0.1.0 requires _macros 0.2.0 [...]
So, because _macros from sdk doesn't exist (could not find package _macros in the Dart SDK) and classy depends on macros ^0.1.0, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on macros: dart pub add macros:^0.0.1

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.