Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributedart_spawner

Runs Dart scripts, files, or URIs inside a new Isolate of the current Dart VM.

pub.devRemove
puby

Run Dart and Flutter commands across multiple projects in the current directory.

pub.devRemove
ScoresHealth6868
Maintenance92 (best)75
Quality100100
Popularity35 (best)31
Community646 (best)
Compatibility8585
UsageDownloads (30 days)5.9k (best)645
Likes1236 (best)
Pub points160 / 160160 / 160
GitHub stars814 (best)
MaintenanceLatest release1.3.1, 9 days ago (best)1.39.2, 7 weeks ago
Major versions in 12 months00
Contributors12 (best)
PublisherUnverifiedrexios.dev
FitPlatformsAll (pure Dart)All (pure Dart)
WASM-readyNoNo
KindPure DartPure Dart
Code generationNoYes
Direct dependencies3 (best)9
LicenseBSD-3-CLAUSEBSD-3-CLAUSE
Setup effortLowLow
JudgementStrengths
  • Can spawn code from external Dart projects or workspaces using their package configs.
  • Handles error and exit code tracking robustly across different VM states.
  • Automatically detects project engines (dart, flutter, fvm).
  • Significantly faster dependency linking with `puby link`.
  • Supports project-level command exclusions and combined exit codes for CI.
Weaknesses
  • Not supported outside the Dart VM or in compiled standalone executables.
  • Relies on directory structure and convention for project discovery.
  • Relative paths passed to `puby exec` require full paths ($PWD) to work correctly.
WarningsNoneNone
dart_spawner vs puby: which Flutter package should you use? | pubscout