Future follow-up to v0.5 Welcome providers (#135); this does not alter that milestone or its issues.
Goal
Let users optionally select maintained external fetch tools for the NMSh welcome surface while keeping Native as an excellent default.
Prefer a small provider model: Native, External Command, or None, with curated preset metadata for maintained tools such as Fastfetch and other justified options. Treat Neofetch as legacy if retained. Avoid a bespoke architecture per executable.
Safety
A custom command requires explicit configuration, bounded timeout/error handling, no hidden shell injection, presentation-only semantics and exclusion from user command history. Installation/setup always requires explicit confirmation through existing discovery flows (#9). NMSh remains useful without any external fetch tool.
Future follow-up to v0.5 Welcome providers (#135); this does not alter that milestone or its issues.
Goal
Let users optionally select maintained external fetch tools for the NMSh welcome surface while keeping Native as an excellent default.
Prefer a small provider model: Native, External Command, or None, with curated preset metadata for maintained tools such as Fastfetch and other justified options. Treat Neofetch as legacy if retained. Avoid a bespoke architecture per executable.
Safety
A custom command requires explicit configuration, bounded timeout/error handling, no hidden shell injection, presentation-only semantics and exclusion from user command history. Installation/setup always requires explicit confirmation through existing discovery flows (#9). NMSh remains useful without any external fetch tool.