pubspec_parse 1.2.3 pubspec_parse: ^1.2.3 copied to clipboard
Simple package for parsing pubspec.yaml files with a type-safe API and rich error reporting.
34
likes
120/ 140
pub points
99%
popularity
We analyzed this package 3 hours ago, and awarded it 120 pub points (of a possible 140):
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
.
10/10 points: 20% or more of the public API has dartdoc comments
13 out of 52 API elements (25.0 %) have documentation comments.
Some symbols that are missing documentation: pubspec_parse
, pubspec_parse.Dependency
, pubspec_parse.GitDependency
, pubspec_parse.GitDependency.GitDependency
, pubspec_parse.GitDependency.GitDependency.fromData
.
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
40/50 points: code has no errors, warnings, lints, or formatting issues
lib/src/pubspec.dart doesn't match the Dart formatter.
To format your files run: dart format .
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
checked_yaml |
^2.0.1 |
2.0.3 | 2.0.3 |
collection |
^1.15.0 |
1.18.0 | 1.18.0 |
json_annotation |
^4.8.0 |
4.9.0 | 4.9.0 |
pub_semver |
^2.0.0 |
2.1.4 | 2.1.4 |
yaml |
^3.0.0 |
3.1.2 | 3.1.2 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
meta |
- | 1.14.0 | 1.14.0 |
path |
- | 1.9.0 | 1.9.0 |
source_span |
- | 1.10.0 | 1.10.0 |
string_scanner |
- | 1.2.0 | 1.2.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
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
Analyzed with Pana 0.22.3
, Dart 3.3.4
.
Check the analysis log for details.