visibility_cached_image 0.1.2
visibility_cached_image: ^0.1.2 copied to clipboard
A Flutter package that efficiently handles loading both network and asset images with advanced memory management techniques.
We analyzed this package 3 days ago, and awarded it 130 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.
0/10 points: 20% or more of the public API has dartdoc comments
3 out of 52 API elements (5.8 %) have documentation comments.
Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API. Document at least 20% of the public API elements.
To highlight public API members missing documentation consider enabling the public_member_api_docs lint.
Some symbols that are missing documentation: visibility_cached_image, visibility_cached_image.ImageCacheEntry, visibility_cached_image.ImageCacheEntry.ImageCacheEntry.new, visibility_cached_image.ImageCacheEntry.accessCount, visibility_cached_image.ImageCacheEntry.data.
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.cn/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
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
async |
any |
2.13.0 | 2.13.0 | |
dio |
any |
5.9.0 | 5.9.0 | |
flutter_hooks |
any |
0.21.3+1 | 0.21.3+1 | |
hive_ce_flutter |
any |
2.3.3 | 2.3.3 | |
uuid |
any |
4.5.1 | 4.5.1 | |
visibility_detector |
any |
0.4.0+2 | 0.4.0+2 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
characters |
- | 1.4.0 | 1.4.1 | |
collection |
- | 1.19.1 | 1.19.1 | |
crypto |
- | 3.0.6 | 3.0.6 | |
dio_web_adapter |
- | 2.1.1 | 2.1.1 | |
ffi |
- | 2.1.4 | 2.1.4 | |
fixnum |
- | 1.1.1 | 1.1.1 | |
hive_ce |
- | 2.15.1 | 2.15.1 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
isolate_channel |
- | 0.2.2+1 | 0.2.2+1 | |
json_annotation |
- | 4.9.0 | 4.9.0 | |
material_color_utilities |
- | 0.11.1 | 0.13.0 | |
meta |
- | 1.16.0 | 1.17.0 | |
mime |
- | 2.0.0 | 2.0.0 | |
path |
- | 1.9.1 | 1.9.1 | |
path_provider |
- | 2.1.5 | 2.1.5 | |
path_provider_android |
- | 2.2.20 | 2.2.20 | |
path_provider_foundation |
- | 2.4.3 | 2.4.3 | |
path_provider_linux |
- | 2.2.1 | 2.2.1 | |
path_provider_platform_interface |
- | 2.1.2 | 2.1.2 | |
path_provider_windows |
- | 2.3.0 | 2.3.0 | |
platform |
- | 3.1.6 | 3.1.6 | |
plugin_platform_interface |
- | 2.1.8 | 2.1.8 | |
source_span |
- | 1.10.1 | 1.10.1 | |
sprintf |
- | 7.0.0 | 7.0.0 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 | |
vector_math |
- | 2.2.0 | 2.2.0 | |
web |
- | 1.1.1 | 1.1.1 | |
xdg_directories |
- | 1.1.0 | 1.1.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
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 5 errors:
UNDEFINED_IDENTIFIER-lib/src/config.dart:179:23- Undefined name 'Namespace'.UNDEFINED_METHOD-lib/src/image_widget.dart:55:23- The method 'useRef' isn't defined for the type 'VisibilityCachedImage'.UNDEFINED_CLASS-lib/src/image_widget.dart:192:14- Undefined class 'ObjectRef'.
Run flutter pub downgrade and then flutter analyze to reproduce the above problem.
You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.23.0, Flutter 3.35.7, Dart 3.9.2.
Check the analysis log for details.