Should General have a guideline or rule preventing registration of vibe-coded packages?

Actually Pkg and registries can already handle name clashes even if the user experience won’t be that great. Nevertheless I can’t really see moving packages around between registries being a viable solution.

There have been removals from General, e.g. a recent package that was never installable for anyone, but unless there is a major shift in the policies for General I don’t see any package removals happen for non-technical reasons with less than the package being malicious or having legal issues, and also then on a case by case basis.

3 Likes