pgmoat 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +2 -2
  2. package/dist/bin.mjs +3310 -3132
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -36,7 +36,7 @@ Or to Claude Desktop (`claude_desktop_config.json`):
36
36
 
37
37
  Passing the URL through `--url-env` keeps the password out of process listings.
38
38
 
39
- Use a dedicated read-only role. pgmoat warns at startup if the role is a superuser or can write.
39
+ Use a dedicated read-only role. pgmoat checks the role at startup. With a `pgmoat.yaml`, it refuses to start if the role is a superuser (PGM-701), has `BYPASSRLS` while row-level security is configured (PGM-702), or owns a protected table without `FORCE ROW LEVEL SECURITY` (PGM-703), unless you pass `--allow-unsafe-role`; every audit entry then records the override. In zero-config mode (a URL and no config file) it warns and continues.
40
40
 
41
41
  ## Add descriptions and hide sensitive data
42
42
 
@@ -94,7 +94,7 @@ Run `pgmoat --help` for all options.
94
94
 
95
95
  - Docs: https://kitalonlabs.com/pgmoat/docs
96
96
  - Source and issues: https://github.com/Kitalon-Labs-LLC/pgmoat
97
- - Security reports: security@kitalonlabs.com
97
+ - Security reports: sowad@kitalonlabs.com
98
98
 
99
99
  ## License
100
100