sunrise_sunset_calc 3.0.0 sunrise_sunset_calc: ^3.0.0 copied to clipboard
Calculates sunrise and sunset time given latitude, longitude, timezone offset and date.
We analyzed this package 2 days ago, and awarded it 140 pub points (of a possible 160):
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: MIT
.
10/10 points: 20% or more of the public API has dartdoc comments
8 out of 8 API elements (100.0 %) have documentation comments.
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.
30/50 points: code has no errors, warnings, lints, or formatting issues
WARNING: This API is available since SDK 2.14.0, but constraints '>=2.12.0 <3.0.0' don't guarantee it.
lib/src/sunrise_sunset_calc_result.dart:17:30
╷
17 │ int get hashCode => Object.hash(sunrise, sunset);
│ ^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/sunrise_sunset_calc_result.dart
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
async |
^2.8.1 |
2.12.0 | 2.12.0 |
vector_math |
^2.1.0 |
2.1.4 | 2.1.4 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
- | 1.19.1 | 1.19.1 |
meta |
- | 1.16.0 | 1.16.0 |
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.15
, Dart 3.5.4
.
Check the analysis log for details.