Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributedetect_unused_code

Fast, zero-dependency Dart and Flutter dead code, assets, and packages remediation engine.

pub.devRemove
import_lint

Defines rules to restrict imports and perform static analysis in Dart code.

pub.devRemove
ScoresHealth65 (best)58
Maintenance93 (best)31
Quality94 (best)93
Popularity2552 (best)
Community646 (best)
Compatibility8585
UsageDownloads (30 days)1.8k9.8k (best)
Likes1128 (best)
Pub points160 / 160 (best)150 / 160
GitHub stars233 (best)
MaintenanceLatest release3.7.0, 14 days ago (best)2.0.0, 7 months ago
Major versions in 12 months21 (best)
Contributors12 (best)
PublisherUnverifiedkawa.dev
FitPlatformsAll (pure Dart)All (pure Dart)
WASM-readyNoNo
KindPure DartPure Dart
Code generationNoNo
Direct dependencies0 (best)8
LicenseMITMIT
Setup effortLowLow
JudgementStrengths
  • Zero external dependencies and fast AST-based analysis.
  • Interactive terminal dashboard (TUI) with dry-run previews and instant rollback.
  • Covers 13 code quality points including commented files, dead classes, assets, and dependencies.
  • Integrates directly into the IDE via analysis server plugins.
  • Provides both CLI support and IDE lint warnings.
  • Customizable glob patterns for targets, sources, and exceptions.
Weaknesses
  • Can require careful configuration via pubspec.yaml exclusions for generated files or dynamic assets to avoid false positives.
  • Requires manual restart of the Dart Analysis Server after updating configuration plugins.
  • Strict Dart SDK version requirement (>=3.10.0 <4.0.0).
WarningsNoneNone
detect_unused_code vs import_lint: which Flutter package should you use? | pubscout