Release

.cursor/rules/better-auth.mdc

@@ -0,0 +1,28 @@
+---
+description: When dealing with auth or authClient related code.
+globs: 
+alwaysApply: false
+---
+Only use auth.ts and auth.api methods serverside. To use them you have to pass Next.js headers as follows:
+auth.api.hasPermission({
+  headers: await headers(),
+    body: {
+      permissions: {
+        project: ["create"] // This must match the structure in your access control
+      }
+    }
+});
+
+
+
+ Only use auth-client.ts and authClient on clienside. You do not need to pass headers, it's already contextually aware.
+
+ const canCreateProject = await authClient.organization.hasPermission({
+    permissions: {
+        project: ["create"]
+    }
+})
+
+
+For the full list of methods/supported actions reference:
+https://www.better-auth.com/docs/plugins/organization

.cursor/rules/imports.mdc

@@ -0,0 +1,6 @@
+---
+description: 
+globs: 
+alwaysApply: true
+---
+Always remove unused imports.

.cursor/rules/react-code.mdc

@@ -1,11 +1,12 @@
 ---
 description: 
-globs: 
-alwaysApply: true
+globs: *.tsx
+alwaysApply: false
 ---
 When writing React code follow these standards:
 
 - Always export a named component
 - Always name components in PascalCase i.e (MyComponent)
 - Always name files that export components in PascalCase
 - Always try to keep components small and modular
+- Always use sonner instead of toast.

.cursor/rules/translation-rules.mdc

@@ -22,4 +22,12 @@ This corresponds to the key of the object inside [en.ts](mdc:apps/app/src/locale
 If there is a linting error, likely this key doesn't exist in [en.ts](mdc:apps/app/src/locales/en.ts) yet.
 
 
-Also never add translations directly in en.ts, check the files it links to, it should always be in a subfile.
+Also never add translations directly in en.ts, check the files it links to, it should always be in a subfile.
+
+NEVER add a {} object as a second param on translation calls, this is not valid syntax.
+
+BAD
+`t("vendors.tasks.title", {})`
+
+GOOD
+`t("vendors.tasks.title")`

.github/workflows/database-migrations-dev.yml

@@ -0,0 +1,34 @@
+name: Database Migrations Dev
+
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch: # Allows manual triggering
+
+env:
+  BUN_VERSION: "1.0.26"
+
+jobs:
+  migrate:
+    name: Run Database Migrations
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v1
+        with:
+          bun-version: ${{ env.BUN_VERSION }}
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Apply database migrations
+        env:
+          DATABASE_URL: ${{ secrets.DATABASE_URL_DEV }}
+        run: |
+          cd packages/db
+          bunx prisma migrate deploy

.github/workflows/database-migrations.yml

@@ -3,7 +3,7 @@ name: Database Migrations
 on:
   push:
     branches:
-      - main
+      - release
   workflow_dispatch: # Allows manual triggering
 
 env:

.github/workflows/trigger-tasks-deploy-dev.yml

@@ -0,0 +1,38 @@
+name: Deploy to Trigger.dev (dev)
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Use Node.js 20.x
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20.x"
+
+      - name: Setup Bun
+        uses: oven-sh/setup-bun@v1
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Generate Prisma client
+        working-directory: ./packages/db
+        run: bunx prisma generate
+
+      - name: 🚀 Deploy Trigger.dev
+        working-directory: ./apps/app
+        env:
+          TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
+          SECRET_KEY: ${{ secrets.SECRET_KEY }}
+          VERCEL_ACCESS_TOKEN: ${{ secrets.VERCEL_ACCESS_TOKEN }}
+          VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}
+          VERCEL_TEAM_ID: ${{ secrets.VERCEL_TEAM_ID }}
+        run: bunx trigger.dev@latest deploy --env staging

.github/workflows/trigger-tasks-deploy.yml

@@ -3,7 +3,7 @@ name: Deploy to Trigger.dev (prod)
 on:
   push:
     branches:
-      - main
+      - release
 
 jobs:
   deploy:

README.md

@@ -32,6 +32,12 @@ We're building the first open source compliance automation platform that helps c
 
 We transform compliance from a vendor checkbox into an engineering problem solved through code. Our platform automates evidence collection, policy management, and control implementation while keeping you in control of your data and infrastructure.
 
+## Recognition
+
+#### [ProductHunt](https://www.producthunt.com/posts/comp-ai)
+
+<a href="https://www.producthunt.com/posts/comp-ai?embed=true&utm_source=badge-top-post-badge&utm_medium=badge&utm_souce=badge-comp&#0045;ai" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=944698&theme=light&period=daily&t=1745500415958" alt="Comp&#0032;AI - The&#0032;open&#0032;source&#0032;Vanta&#0032;&#0038;&#0032;Drata&#0032;alternative | Product Hunt" style="width: 250px; height: 54px;" width="250" height="54" /></a>
+
 ### Built With
 
 - [Next.js](https://nextjs.org/?ref=trycomp.ai)