cellular_automata 1.0.2

cellular_automata: ^1.0.2 copied to clipboard

10/10 points: Provide a valid pubspec.yaml

0/5 points: Provide a valid README.md

   ╷
53 │ <p>See the <code>demos/</code> <a href="https://github.com/jimmyff/cellular_automata_web/tree/master/demos">folder</a> for demos. You can try the <a href="http://jimmyff.github.io/cellular_automata">hosted demos</a> here.</p>
   │                                                                                                                                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   ╵

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.

10/10 points: Package has an example

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.dev/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:

The lower bound of "sdk: '>=2.0.0-dev.61.0 <3.0.0'" must be 2.12.0'
or higher to enable null safety.

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

  ╷
8 │   sdk: '>=2.0.0-dev.61.0 <3.0.0'
  │        ^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵

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

  ╷
8 │   sdk: '>=2.0.0-dev.61.0 <3.0.0'
  │        ^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵

0/20 points: Compatible with dependency constraint lower bounds

dart pub downgrade failed with:

OUT:
Resolving dependencies...
ERR:
The lower bound of "sdk: '>=2.0.0-dev.61.0 <3.0.0'" must be 2.12.0'
or higher to enable null safety.

The current Dart SDK (3.6.0) only supports null safety.

For details, see https://dart.dev/null-safety

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.