atmospeed 1.0.2 atmospeed: ^1.0.2 copied to clipboard
Calculate standard and non-standard atmosphere properties and speed conversions. Uses 1976 US Standard Atmosphere definitions.
We analyzed this package 41 hours ago, and awarded it 150 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
Issue tracker URL doesn't exist.
At the time of the analysis https://github.com/aeroperf/atmospeed/issues
was unreachable. Make sure that the website is reachable via HEAD
requests.
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
.
10/10 points: 20% or more of the public API has dartdoc comments
38 out of 42 API elements (90.5 %) have documentation comments.
Some symbols that are missing documentation: atmospeed.ConvertSpeed.convertSpeed
, atmospeed.Speed.type
, atmospeed.Speed.unitSpeed
, atmospeed.Speed.value
.
10/10 points: Package has an example
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
This package is compatible with runtime wasm
, and will be rewarded additional points in a future version of the scoring model.
See https://dart.dev/web/wasm for details.
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: Dangling library doc comment.
lib/src/constants.dart:1:1
╷
1 │ /// Atmospheric constants
│ ^^^^^^^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/constants.dart
10/10 points: All of the package dependencies are supported in the latest version
No dependencies.
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
10/10 points: Package supports latest stable Dart and Flutter SDKs
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade
does not expose any static analysis error.
Analyzed with Pana 0.22.17
, Dart 3.6.0
.
Check the analysis log for details.