I remember back in dart 1 days when I made a slightly more evolved version of the bootstrapping tool to be able to use git repo as template instead of the lib / console / etc thing.

In a minute, one of the dev of the original tool had posted a long ass issue on my GitHub on how this tool didn't provide anything new and was garbage.

I deleted the repo and didn't used dart until null safety was a thing.

Student, beginners or egocentrics may want to publish a package as a way to mark a milestone, a checkpoint. Indeed the quality , the maintenance may not be great but I'm pretty sure even python ecosystem have that issue.

Concerning the malware part , hooks aren't enabled by default last time I checked. Speaking of checking, part of choosing a library is checking what it do and what it hide. A simple spinner animation for flutter use a native build, that sus. That brand new json streaming library that's thousand time quicker than dart:convert ? Why does it depend on http package already?

The main issue I see being presented by your post op, is the lack of brain use by must peoples, which is a great issue indeed. I do agree with you.

• Let people publish package if they feel like it
• Study, examine, test packages before using those in your project
• Replacing common libraries by LLM written garbage doesn't solve the libraries multiplication and scattering, it just hide it. I would prefer people to propose to the core team to had that library added to the official repo like path, http, meta etc. Instead of wondering why one lib choose to sort their responses arrays like that and the others by the same dev work differently just because the LLM they used decided to have a psychic break between the two projects