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.

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

Dependency resolution failed, unable to run dartdoc.

0/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:

Because excel >=4.0.6 depends on archive ^3.6.1 and lottie >=3.3.1 depends on archive ^4.0.0, excel >=4.0.6 is incompatible with lottie >=3.3.1.
So, because panoptic_widgets depends on both excel ^4.0.6 and lottie ^3.3.1, version solving failed.

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:
Because excel >=4.0.6 depends on archive ^3.6.1 and lottie >=3.3.1 depends on archive ^4.0.0, excel >=4.0.6 is incompatible with lottie >=3.3.1.
So, because panoptic_widgets depends on both excel ^4.0.6 and lottie ^3.3.1, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on lottie: flutter pub add lottie:^3.3.0
Failed to update packages.

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:
Because excel >=4.0.6 depends on archive ^3.6.1 and lottie >=3.3.1 depends on archive ^4.0.0, excel >=4.0.6 is incompatible with lottie >=3.3.1.
So, because panoptic_widgets depends on both excel ^4.0.6 and lottie ^3.3.1, version solving failed.


You can try the following suggestion to make the pubspec resolve:
* Consider downgrading your constraint on lottie: flutter pub add lottie:^1.0.0
Failed to update packages.

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.