Base58Check and regular Base58 encoding implementation for Dart using dart:convert interface.
Support Dart v2.
- Simplified interface to remove external SHA-256 requirement
- Created Base58CheckCodec.bitcoin() constructor
- Made Base58CheckCodec store instances of the encoder and decoder for performance improvement
- Updated to new collection and crypto interfaces
- Initial version
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: base58check: ^1.0.1
2. Install it
You can install packages from the command line:
$ pub get
$ flutter pub get
Alternatively, your editor might support
pub get or
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Oct 11, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.5.1
- pana: 0.12.21
Detected platforms: Flutter, web, other
No platform restriction found in primary library
lib/base58.dart. (-8.17 points)
lib/base58.dart reported 17 hints, including:
line 6 col 1: Prefer using /// for doc comments.
line 17 col 21: Don't type annotate initializing formals.
line 26 col 1: Prefer using /// for doc comments.
line 32 col 23: Don't type annotate initializing formals.
line 36 col 9: Use isEmpty instead of length
lib/base58check.dart. (-2.96 points)
lib/base58check.dart reported 6 hints, including:
line 14 col 28: Don't type annotate initializing formals.
line 14 col 46: Don't type annotate initializing formals.
line 24 col 1: Prefer using /// for doc comments.
line 44 col 20: Don't type annotate initializing formals.
line 66 col 28: Don't type annotate initializing formals.
Package is getting outdated. (-16.16 points)
The package was last published 60 weeks ago.
The package description is too short. (-11 points)
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.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
base58check.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.