To have a good set of base rules we can extend from, we could use eslint-config-standard (https://github.com/standard/eslint-config-standard), and adjust for our purposes as necessary. This would result in a much stricter linting config, so if adopted, we should publish this change with a new major version.
Not everyone needs a stricter set, not everyone needs a lax set, this will always be an opinionated compromise. Every project needs to tune the rules for themselves.
If we base our rules on standard (see here https://standardjs.com/) we should check if we need to add, substract, or modify anything at all, or if we really just re-export their rules or just advice to use them and deprecate our package.
There is so far no reason not to provide a lax and a strict set based on the default and the "standard" rules if there is an application for both.
Not just we, but also our customers use these rules (which is why we open sourced them).
To have a good set of base rules we can extend from, we could use eslint-config-standard (https://github.com/standard/eslint-config-standard), and adjust for our purposes as necessary. This would result in a much stricter linting config, so if adopted, we should publish this change with a new major version.