Why this matters
The PUBLIC pseudo-role covers every current and future role in the database. Privilege grants should name roles explicitly. `REVOKE ... FROM PUBLIC` is unaffected — revoking implicit grants is good hygiene.
Examples
Incorrect
GRANT SELECT ON users TO PUBLIC;Correct
GRANT SELECT ON users TO reporting;REVOKE ALL ON users FROM PUBLIC;Configure it
// eslint.config.js
import postgresql from "eslint-plugin-postgresql";
export default [
{
files: ["**/*.sql"],
languageOptions: {
parser: postgresql.configs.recommended.languageOptions.parser,
},
plugins: { postgresql },
rules: {
"postgresql/no-grant-to-public": "warn",
},
},
]; Options
Edit the SQL — only no-grant-to-public is enabled.
Pre-filled with the first incorrect example. Toggle off in the rule shelf to see how the diagnostic disappears.
Diagnostics
No issues found.
2 rules enabled.
Rule under test
no-grant-to-public — plus no-syntax-error as a safety net.