insforge
Facilitates frontend integration with InsForge SDK for database queries, authentication, and real-time messaging in web applications.
Install this skill
Security score
The insforge skill was audited on Jun 11, 2026 and we found 24 security issues across 3 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Webhook reference - potential data exfiltration
| 154 | | [payments](../insforge-cli/references/payments/overview.md) | Configuring Stripe/Razorpay keys, syncing provider catalog, setting up webhooks, and |
Webhook reference - potential data exfiltration
| 226 | - **Payment RLS**: Before payment UI, add app-specific RLS on provider runtime tables. Stripe uses `payments.stripe_checkout_sessions` and `payments.stripe_customer_portal_sessions`; Razorpay uses `pa |
Access to .env file
| 27 | Before using the SDK, create a `.env` file (or `.env.local` for Next.js) in your project root with your InsForge URL and anon key. |
Access to .env file
| 42 | 4. **Write both values** to the `.env` file using the correct framework prefix (see table below). |
Access to .env file
| 48 | | Framework | `.env` file | Variables | Access Pattern | |
Access to .env file
| 50 | | **Next.js** | `.env.local` | `NEXT_PUBLIC_INSFORGE_URL`, `NEXT_PUBLIC_INSFORGE_ANON_KEY` | `process.env.NEXT_PUBLIC_*` | |
Access to .env file
| 51 | | **Vite** (React, Vue, Svelte) | `.env` | `VITE_INSFORGE_URL`, `VITE_INSFORGE_ANON_KEY` | `import.meta.env.VITE_*` | |
Access to .env file
| 52 | | **Astro** | `.env` | `PUBLIC_INSFORGE_URL`, `PUBLIC_INSFORGE_ANON_KEY` | `import.meta.env.PUBLIC_*` | |
Access to .env file
| 53 | | **SvelteKit** | `.env` | `PUBLIC_INSFORGE_URL`, `PUBLIC_INSFORGE_ANON_KEY` | `import { env } from '$env/dynamic/public'` | |
Access to .env file
| 54 | | **Create React App** | `.env` | `REACT_APP_INSFORGE_URL`, `REACT_APP_INSFORGE_ANON_KEY` | `process.env.REACT_APP_*` | |
Access to .env file
| 55 | | **Node.js / Server** | `.env` | `INSFORGE_URL`, `INSFORGE_ANON_KEY` | `process.env.*` | |
Access to .env file
| 57 | Example `.env.local` for Next.js: |
Access to .env file
| 64 | > **Important:** Keep `.env` files local. Add `.env`, `.env.local`, and `.env*.local` to your `.gitignore` and keep `.env.example` for documenting required variables. |
Access to .env file
| 74 | baseUrl: process.env.NEXT_PUBLIC_INSFORGE_URL, |
Access to .env file
| 75 | anonKey: process.env.NEXT_PUBLIC_INSFORGE_ANON_KEY |
Access to .env file
| 85 | baseUrl: import.meta.env.VITE_INSFORGE_URL, |
Access to .env file
| 86 | anonKey: import.meta.env.VITE_INSFORGE_ANON_KEY |
Access to .env file
| 96 | baseUrl: import.meta.env.PUBLIC_INSFORGE_URL, |
Access to .env file
| 97 | anonKey: import.meta.env.PUBLIC_INSFORGE_ANON_KEY |
Access to .env file
| 107 | baseUrl: process.env.INSFORGE_URL, |
Access to .env file
| 108 | apiKey: process.env.INSFORGE_API_KEY, |
Access to .env file
| 200 | > ⚠ **After `branch create` or `branch switch`**, update the app's InsForge URL and anon-key env values, then **restart your dev server** (or re-source `.env`) so the SDK talks to the selected branch |
External URL reference
| 40 | 3. **Get the URL** from the `oss_host` field in `.insforge/project.json` (e.g., `https://myapp.us-east.insforge.app`). |
External URL reference
| 60 | NEXT_PUBLIC_INSFORGE_URL=https://your-appkey.us-east.insforge.app |