Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributefreezed

Code generation for immutable classes, tagged unions, and cloning without boilerplate.

pub.devRemove
maybe_copy_with

Write ergonomic copyWith methods for immutable models without build_runner.

pub.devRemove
ScoresHealth96 (best)41
Maintenance92 (best)7
Quality100100
Popularity93 (best)17
Community100 (best)6
Compatibility100100
UsageDownloads (30 days)3.1M (best)1.4k
Likes4.5k (best)9
Pub points160 / 160160 / 160
GitHub stars2.2k (best)0
MaintenanceLatest release4.0.3, 5 weeks ago (best)1.0.0, a year ago
Major versions in 12 months00
Contributors100+ (best)1
Publisherdash-overflow.netUnverified
FitPlatformsAndroid, iOS, Windows, macOS, LinuxAll (pure Dart)
WASM-readyNoYes
KindFlutter widgetsPure Dart
Code generationYesYes
Direct dependencies110 (best)
LicenseMITMIT
Setup effortMediumLow
JudgementStrengths
  • Significantly reduces boilerplate code for data models.
  • Supports union types, deep cloning, default values, and asserts.
  • Integrates seamlessly with json_serializable for de/serialization.
  • Zero dependencies and lightweight.
  • No code generation or build_runner setup required.
  • Solves the nullability dilemma in copyWith methods cleanly.
Weaknesses
  • Requires running a code generator (build_runner) during development.
  • Can introduce steep debugging curves when generated files go out of sync.
  • Fields must still be manually listed and implemented in copyWith.
  • Requires wrapping nullable field arguments with .maybe().
WarningsNoneNone
freezed vs maybe_copy_with: which Flutter package should you use? | pubscout