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

Would it be possible to introduce some automated checks for the newly registered packages, that:

  • Package has a test suite.
  • Package has some documentation. Maybe relate the extent of required documenation to the code size. At least a description of what the package does should be provided in all cases.
  • Each exported name has docstrings.

I don’t think it is asking too much from the package authors, but if some of it is difficult to implement (e.g. tests for interactive packages), then it can be resolved by a human.