edid 0.0.1 edid: ^0.0.1 copied to clipboard
An EDID parser
We analyzed this package 7 days ago, and awarded it 130 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
The package description is too short.
Add more detail to the description
field of pubspec.yaml
. Use 60 to 180 characters to describe the package, what it does, and its target use case.
-
pubspec.yaml
doesn't have ahomepage
entry. -
pubspec.yaml
doesn't have arepository
entry.
0/5 points: Provide a valid README.md
No `README.md` found.
The README.md
file should inform others about your project, what it does, and how they can use it. Check out the guidelines on Writing great package pages.
0/5 points: Provide a valid CHANGELOG.md
No `CHANGELOG.md` found.
Changelog entries help developers follow the progress of your package. Check out the Dart conventions for Maintaining a package changelog.
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
0 out of 0 API elements (100.0 %) have documentation comments.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add 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.
50/50 points: code has no errors, warnings, lints, or formatting issues
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.15
, Dart 3.5.4
.
Check the analysis log for details.