Having tried to use a few serverless plugins lately, to be respectful I won't name them as I appreciate the effort of contributors, it would be good to see some community standards before they are accepted on the official list. Often you'll see tickets or threads on the forum pointing to a plugin to use for a particular plugin which at worst does not work at all, varies from serverless standards (names over refs) or does not support LTS versions of node.js. As these are recommended on this list it produces mistrust on the quality of the serverless ecosystem.

Some of my grievances are:

• inconsistent semver
• lack of changelog and contributing documentation
• lack of CI testing (or tests altogether)
• unstated support for node and npm versions.

I support the proposal made last year to create a community plugin organisation (�serverless-plugins) to adopt widely used plugins so you don't have a single point of failure on one contributor to accept patches, or worse, release breaking changes unexpectedly. These packages can be managed to a higher standard by common contributors although the bare minimum could be to instructing (teaching perhaps) plugin developers, hoping to be on the list, to use a model for minimal acceptable standards (Travis CI builds for LTS versions of node, testing, linting, code quality tools, changelogs).