lzy_codec 0.1.4
lzy_codec: ^0.1.4 copied to clipboard
一種變長文本編解碼方案,支持對Unicode進行編解碼。編解碼效率、存儲空間全面優於UTF-8。
We analyzed this package 4 days ago, and awarded it 140 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 50 to 180 characters to describe the package, what it does, and its target use case.
The package description contains too many non-ASCII characters.
The site uses English as its primary language. The content of the description field in your package's pubspec.yaml should primarily contain characters used in English.
Homepage URL doesn't exist.
At the time of the analysis https://github.com/lizongying/lzy_codec_dart 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: MIT.
10/10 points: 20% or more of the public API has dartdoc comments
7 out of 10 API elements (70.0 %) have documentation comments.
Some symbols that are missing documentation: lzy_codec, lzy_codec.Lzy, lzy_codec.Lzy.Lzy.new.
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
WASM-ready: This package is compatible with runtime wasm. 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.23.19, Dart 3.13.5.
Check the analysis log for details.