claimable-postgres
Provisions instant temporary Postgres databases for quick prototyping and development without requiring login or credit card.
Install this skill
Security score
The claimable-postgres skill was audited on May 14, 2026 and we found 26 security issues across 3 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Curl to non-GitHub URL
| 15 | curl -s -X POST "https://pg.new/api/v1/database" \ |
Curl to non-GitHub URL
| 39 | curl -s -X POST "https://pg.new/api/v1/database" \ |
Curl to non-GitHub URL
| 69 | curl -s "https://pg.new/api/v1/database/{id}" |
Access to .env file
| 20 | Parse `connection_string` and `claim_url` from the JSON response. Write `connection_string` to the project's `.env` as `DATABASE_URL`. |
Access to .env file
| 27 | - **CLI** (`npx get-db@latest --yes`): Provisions and writes `.env` in one command. Convenient when Node.js is available and the user wants a simple setup. |
Access to .env file
| 88 | Provisions a database and writes the connection string to `.env` in one step. Always use `@latest` and `--yes` (skips interactive prompts that would stall the agent). |
Access to .env file
| 92 | Check if `DATABASE_URL` (or the chosen key) already exists in the target `.env`. The CLI exits without provisioning if it finds the key. |
Access to .env file
| 97 | 2. Use `--env` to write to a different file (e.g. `--env .env.local`). |
Access to .env file
| 107 | | `--env` | `-e` | .env file path | `./.env` | |
Access to .env file
| 118 | The CLI writes to the target `.env`: |
Access to .env file
| 152 | 4. **Write .env:** Write `DATABASE_URL=<connection_string>` to the project's `.env` (or the user's preferred file and key). Do not overwrite an existing key without confirmation. |
Access to .env file
| 162 | 1. **Check .env:** Check the target `.env` for an existing `DATABASE_URL` (or chosen key). If present, do not run. Offer remove, `--env`, or `--key` and get confirmation. |
Access to .env file
| 167 | npx get-db@latest --yes --ref agent-skills --env .env.local --seed ./schema.sql |
Access to .env file
| 177 | - Where the connection string was written (e.g. `.env`) |
Access to .env file
| 179 | - The claim URL (from `.env` or API response) |
Access to .env file
| 187 | - **CLI:** `npx get-db@latest claim` reads the claim URL from `.env` and opens the browser automatically. |
Access to .env file
| 218 | - After writing credentials to an .env file, check that it's covered by .gitignore. If not, warn the user. Do not modify `.gitignore` without confirmation. |
External URL reference
| 15 | curl -s -X POST "https://pg.new/api/v1/database" \ |
External URL reference
| 30 | - **Browser**: User cannot run CLI or API. Direct to https://pg.new. |
External URL reference
| 34 | **Base URL:** `https://pg.new/api/v1` |
External URL reference
| 39 | curl -s -X POST "https://pg.new/api/v1/database" \ |
External URL reference
| 59 | "claim_url": "https://pg.new/claim/019beb39-...", |
External URL reference
| 69 | curl -s "https://pg.new/api/v1/database/{id}" |
External URL reference
| 123 | PUBLIC_POSTGRES_CLAIM_URL=https://pg.new/claim/... |
External URL reference
| 143 | For Vite projects, `vite-plugin-db` auto-provisions a database on `vite dev` if `DATABASE_URL` is missing. Install with `npm install -D vite-plugin-db`. See the [Claimable Postgres docs](https://neon. |
External URL reference
| 150 | 2. **Provision:** POST to `https://pg.new/api/v1/database` with `{"ref": "agent-skills"}`. |