ESLint vs StandardJS - which enforces cleaner code?

Just finished setting up a new k3s cluster for our dev team's CI pipeline. Need to standardize the JS linting across all our microservices. The eternal debate: ESLint or StandardJS?

I've used ESLint with a custom config before, but StandardJS's zero-config approach is tempting for consistency. Which one actually enforces cleaner code in a real project? I'm leaning towards ESLint because you can tailor it, like adding specific rules for our Node.js services.

Example of our current ESLint config snippet:
```json
{
"extends": ["eslint:recommended"],
"rules": {
"no-unused-vars": "error",
"prefer-const": "warn"
}
}
```

But does StandardJS's strict no-semicolon rule actually lead to fewer bugs, or is it just style? Curious what others are running in production.