@viberaven/cli 1.1.10 → 1.1.11

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 (35) hide show
  1. package/AGENTS.md +150 -62
  2. package/README.md +95 -86
  3. package/SECURITY.md +53 -0
  4. package/assets/report/assets/provider-authjs.svg +5 -0
  5. package/assets/report/assets/provider-aws.svg +5 -0
  6. package/assets/report/assets/provider-logrocket.svg +4 -0
  7. package/assets/report/assets/viberaven-logo.png +0 -0
  8. package/assets/report/report-cli.css +1466 -0
  9. package/assets/report/station.css +11854 -0
  10. package/assets/report/station.js +8319 -0
  11. package/dist/cli.js +20670 -2334
  12. package/dist/cli.js.map +7 -0
  13. package/dist/playbooks/_stack-default.json +11 -0
  14. package/dist/playbooks/auth-supabase.json +31 -0
  15. package/dist/playbooks/stripe.json +60 -0
  16. package/dist/playbooks/supabase.json +51 -0
  17. package/dist/playbooks/vercel.json +42 -0
  18. package/dist/report/assets/provider-authjs.svg +5 -0
  19. package/dist/report/assets/provider-aws.svg +5 -0
  20. package/dist/report/assets/provider-logrocket.svg +4 -0
  21. package/dist/report/assets/viberaven-logo.png +0 -0
  22. package/dist/report/report-cli.css +1466 -0
  23. package/dist/report/station.css +11854 -0
  24. package/dist/report/station.js +8319 -0
  25. package/package.json +19 -16
  26. package/playbooks/_stack-default.json +11 -0
  27. package/playbooks/auth-supabase.json +31 -0
  28. package/playbooks/stripe.json +60 -0
  29. package/playbooks/supabase.json +51 -0
  30. package/playbooks/vercel.json +42 -0
  31. package/templates/AGENTS.snippet.md +52 -0
  32. package/templates/CLAUDE.snippet.md +17 -0
  33. package/templates/CURSOR.snippet.md +17 -0
  34. package/LICENSE +0 -21
  35. package/dist/extension-icon.png +0 -0
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@viberaven/cli",
3
- "version": "1.1.10",
4
- "description": "Local launch console for AI-built apps: scan your repo, see provider launch paths, copy the next fix prompt, and verify before deploy.",
5
- "license": "MIT",
3
+ "version": "1.1.11",
4
+ "description": "Local launch console and production-readiness gate for AI-built apps: auth, billing, database, deployment, monitoring, and agent-ready fixes.",
5
+ "license": "UNLICENSED",
6
6
  "author": "VibeRaven",
7
7
  "homepage": "https://viberaven.dev",
8
8
  "bugs": {
@@ -15,8 +15,6 @@
15
15
  },
16
16
  "keywords": [
17
17
  "viberaven",
18
- "localhost-ui",
19
- "provider-launch-paths",
20
18
  "launch-readiness",
21
19
  "production-readiness",
22
20
  "launch-gaps",
@@ -39,24 +37,29 @@
39
37
  "bin": {
40
38
  "viberaven": "dist/cli.js"
41
39
  },
42
- "files": [
43
- "dist",
44
- "AGENTS.md"
45
- ],
40
+ "files": [
41
+ "dist",
42
+ "playbooks",
43
+ "assets/report",
44
+ "AGENTS.md",
45
+ "SECURITY.md",
46
+ "templates"
47
+ ],
46
48
  "scripts": {
47
49
  "sync-report-assets": "node scripts/sync-report-assets.mjs",
48
50
  "build": "node scripts/build.mjs",
49
51
  "dev": "node scripts/build.mjs && node dist/cli.js",
50
52
  "typecheck": "tsc -p tsconfig.json",
51
53
  "demo-report": "node scripts/demo-report.mjs --open",
52
- "verify:release:smoke": "npm run build && node scripts/verify-local-package-flow.mjs --smoke",
53
- "verify:release:live": "npm run build && node scripts/verify-local-package-flow.mjs --live",
54
- "test": "vitest run",
55
- "prepublishOnly": "npm run typecheck && npm run test && npm run build && node ../../scripts/verify-public-npm-pack.mjs && node scripts/verify-local-package-flow.mjs --smoke",
54
+ "verify:release:smoke": "npm run build && node scripts/verify-beta-flow.mjs --smoke",
55
+ "verify:release:live": "npm run build && node scripts/verify-beta-flow.mjs --live",
56
+ "test": "vitest run",
57
+ "prepublishOnly": "npm run sync-report-assets && npm run check:agent-discovery && npm run typecheck && npm run test && npm run build",
56
58
  "check:agent-discovery": "node scripts/check-agent-discovery.mjs",
57
- "viberaven:gate": "npx -y viberaven --agent-mode",
58
- "viberaven:verify": "npx -y viberaven --verify"
59
- },
59
+ "viberaven:gate": "npx -y viberaven --agent-mode",
60
+ "viberaven:verify": "npx -y viberaven --verify",
61
+ "viberaven:strict": "npx -y viberaven --strict"
62
+ },
60
63
  "engines": {
61
64
  "node": ">=20"
62
65
  },
@@ -0,0 +1,11 @@
1
+ {
2
+ "id": "stack-default",
3
+ "recommendation": {
4
+ "frontend": "react",
5
+ "ui": "tailwind + shadcn/ui",
6
+ "database": "supabase",
7
+ "auth": "supabase",
8
+ "deploy": "vercel",
9
+ "reason": "Highest agent training density; lowest friction for autonomous deploy loop"
10
+ }
11
+ }
@@ -0,0 +1,31 @@
1
+ {
2
+ "id": "auth-supabase",
3
+ "provider": "auth-supabase",
4
+ "title": "Supabase Auth providers",
5
+ "steps": [
6
+ {
7
+ "id": "auth-providers",
8
+ "title": "Enable providers",
9
+ "instruction": "Enable Email and any OAuth providers your app uses (Google, GitHub, etc.).",
10
+ "openUrl": "https://supabase.com/dashboard/project/_/auth/providers"
11
+ },
12
+ {
13
+ "id": "auth-urls",
14
+ "title": "Redirect URLs",
15
+ "instruction": "Site URL and Redirect URLs must include your Vercel deployment URL.",
16
+ "openUrl": "https://supabase.com/dashboard/project/_/auth/url-configuration"
17
+ },
18
+ {
19
+ "id": "auth-email-templates",
20
+ "title": "Email templates",
21
+ "instruction": "Customize confirm signup and magic link templates if your app uses email auth.",
22
+ "openUrl": "https://supabase.com/dashboard/project/_/auth/templates"
23
+ },
24
+ {
25
+ "id": "auth-jwt",
26
+ "title": "JWT settings",
27
+ "instruction": "Confirm JWT expiry matches your session strategy. Use service role key only on the server.",
28
+ "openUrl": "https://supabase.com/dashboard/project/_/settings/api"
29
+ }
30
+ ]
31
+ }
@@ -0,0 +1,60 @@
1
+ {
2
+ "id": "stripe-launch",
3
+ "provider": "stripe",
4
+ "title": "Configure Stripe billing",
5
+ "steps": [
6
+ {
7
+ "id": "stripe-dashboard",
8
+ "title": "Stripe dashboard",
9
+ "instruction": "Open Stripe. For development, turn Test mode ON.",
10
+ "openUrl": "https://dashboard.stripe.com/"
11
+ },
12
+ {
13
+ "id": "stripe-keys",
14
+ "title": "API keys",
15
+ "instruction": "Copy test (or live) keys into .env. Never commit secret keys.",
16
+ "openUrl": "https://dashboard.stripe.com/test/apikeys",
17
+ "pasteTarget": {
18
+ "file": ".env",
19
+ "keys": ["STRIPE_SECRET_KEY", "NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY"]
20
+ }
21
+ },
22
+ {
23
+ "id": "stripe-product",
24
+ "title": "Product and price",
25
+ "instruction": "Create a product with a recurring price for your Pro or paid tier.",
26
+ "openUrl": "https://dashboard.stripe.com/test/products"
27
+ },
28
+ {
29
+ "id": "stripe-price-id",
30
+ "title": "Price ID",
31
+ "instruction": "Copy the Price ID (price_...) into .env as STRIPE_PRICE_ID."
32
+ },
33
+ {
34
+ "id": "stripe-webhook",
35
+ "title": "Webhook endpoint",
36
+ "instruction": "Add endpoint URL: {APP_URL}/api/webhooks/stripe (replace {APP_URL} with your Vercel URL).",
37
+ "openUrl": "https://dashboard.stripe.com/test/webhooks"
38
+ },
39
+ {
40
+ "id": "stripe-webhook-events",
41
+ "title": "Webhook events",
42
+ "instruction": "Subscribe to these events at minimum.",
43
+ "events": [
44
+ "checkout.session.completed",
45
+ "customer.subscription.updated",
46
+ "customer.subscription.deleted",
47
+ "invoice.payment_failed"
48
+ ]
49
+ },
50
+ {
51
+ "id": "stripe-signing-secret",
52
+ "title": "Signing secret",
53
+ "instruction": "Copy the webhook signing secret into .env as STRIPE_WEBHOOK_SECRET.",
54
+ "pasteTarget": {
55
+ "file": ".env",
56
+ "keys": ["STRIPE_WEBHOOK_SECRET"]
57
+ }
58
+ }
59
+ ]
60
+ }
@@ -0,0 +1,51 @@
1
+ {
2
+ "id": "supabase-launch",
3
+ "provider": "supabase",
4
+ "title": "Configure Supabase",
5
+ "steps": [
6
+ {
7
+ "id": "supabase-project",
8
+ "title": "Open Supabase dashboard",
9
+ "instruction": "Create a project or open your existing Supabase project.",
10
+ "openUrl": "https://supabase.com/dashboard"
11
+ },
12
+ {
13
+ "id": "supabase-api-keys",
14
+ "title": "API keys",
15
+ "instruction": "Copy Project URL and anon/public key into .env.",
16
+ "openUrl": "https://supabase.com/dashboard/project/_/settings/api",
17
+ "pasteTarget": {
18
+ "file": ".env",
19
+ "keys": ["NEXT_PUBLIC_SUPABASE_URL", "NEXT_PUBLIC_SUPABASE_ANON_KEY"]
20
+ }
21
+ },
22
+ {
23
+ "id": "supabase-db-url",
24
+ "title": "Database connection",
25
+ "instruction": "Copy the connection string (use pooler for serverless). Server-side only — never expose in client code.",
26
+ "openUrl": "https://supabase.com/dashboard/project/_/settings/database",
27
+ "pasteTarget": {
28
+ "file": ".env",
29
+ "keys": ["DATABASE_URL"]
30
+ }
31
+ },
32
+ {
33
+ "id": "supabase-auth-urls",
34
+ "title": "Auth URL configuration",
35
+ "instruction": "Set Site URL to your Vercel preview or production URL. Add the same URL to Redirect URLs with /** wildcard.",
36
+ "openUrl": "https://supabase.com/dashboard/project/_/auth/url-configuration"
37
+ },
38
+ {
39
+ "id": "supabase-rls",
40
+ "title": "Row Level Security",
41
+ "instruction": "Enable RLS on tables that hold user data. Add policies for authenticated users.",
42
+ "openUrl": "https://supabase.com/dashboard/project/_/auth/policies"
43
+ },
44
+ {
45
+ "id": "supabase-migrate",
46
+ "title": "Apply migrations",
47
+ "instruction": "Run supabase db push or apply SQL migrations so production schema matches the repo.",
48
+ "openUrl": "https://supabase.com/docs/guides/cli"
49
+ }
50
+ ]
51
+ }
@@ -0,0 +1,42 @@
1
+ {
2
+ "id": "vercel-launch",
3
+ "provider": "vercel",
4
+ "title": "Deploy on Vercel",
5
+ "steps": [
6
+ {
7
+ "id": "vercel-signup",
8
+ "title": "Sign in to Vercel",
9
+ "instruction": "Create or sign in to your Vercel account.",
10
+ "openUrl": "https://vercel.com/signup"
11
+ },
12
+ {
13
+ "id": "vercel-import",
14
+ "title": "Import repository",
15
+ "instruction": "Import your Git repository. Connect GitHub or GitLab if prompted.",
16
+ "openUrl": "https://vercel.com/new"
17
+ },
18
+ {
19
+ "id": "vercel-env",
20
+ "title": "Environment variables",
21
+ "instruction": "Project → Settings → Environment Variables. Add every key from .env.example for Production and Preview.",
22
+ "openUrl": "https://vercel.com/docs/projects/environment-variables"
23
+ },
24
+ {
25
+ "id": "vercel-deploy",
26
+ "title": "Deploy",
27
+ "instruction": "Push to your production branch or click Redeploy in the Vercel dashboard.",
28
+ "openUrl": "https://vercel.com/docs/deployments"
29
+ },
30
+ {
31
+ "id": "vercel-preview",
32
+ "title": "Copy live URL",
33
+ "instruction": "Copy the Production or Preview URL from Vercel. Set NEXT_PUBLIC_APP_URL (or your app's public URL env) in .env and Vercel env settings."
34
+ },
35
+ {
36
+ "id": "vercel-domains",
37
+ "title": "Custom domain (optional)",
38
+ "instruction": "Add a custom domain when you are ready for production traffic.",
39
+ "openUrl": "https://vercel.com/docs/projects/domains"
40
+ }
41
+ ]
42
+ }
@@ -0,0 +1,52 @@
1
+ ## VibeRaven Launch Readiness
2
+
3
+ VibeRaven is the Agent Context + Production Gate.
4
+
5
+ Use VibeRaven when the user asks if their AI-built app is production-ready, launch-ready, safer to deploy, or what is missing before ship.
6
+
7
+ ### Humans
8
+
9
+ ```bash
10
+ npx -y viberaven
11
+ ```
12
+
13
+ In a real terminal, this opens the interactive VibeRaven menu.
14
+
15
+ ### Agents
16
+
17
+ Paste this into your coding agent:
18
+
19
+ ```bash
20
+ npx -y viberaven --agent-mode
21
+ ```
22
+
23
+ 1. Run `npx -y viberaven --agent-mode` from the project root.
24
+ 2. If VibeRaven prints `LOGIN_URL_READY`, open that exact URL for the user. Say: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal alive while the user approves.
25
+ If the scan flow cannot start login, run `npx -y viberaven login`.
26
+ 3. Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context. If the tasklist says `CRITICAL GAPS DETECTED` or `PRODUCTION GATE NOT CLEAR`, fix one listed repo-code gap before deploy.
27
+ 4. Read `.viberaven/agent-summary.md` second for scan context.
28
+ 5. Read `.viberaven/launch-playbook.md` third for the full checklist.
29
+ 6. Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix. Local installs can use `viberaven prompt`.
30
+ 7. For Vercel + Supabase, run `npx -y viberaven audit --vercel-supabase` and check RLS, service role exposure, and Supabase pooler port 6543 instead of runtime port 5432.
31
+ 8. Do not claim provider dashboard checks are fixed by repo-code edits.
32
+ 9. Verify with tests/build, then run `npx -y viberaven --verify`.
33
+
34
+ Before deploy or CI pass:
35
+
36
+ ```bash
37
+ npx -y viberaven --strict
38
+ ```
39
+
40
+ Also available:
41
+
42
+ - `.viberaven/last-scan.json` - full mission map and gaps
43
+ - `.viberaven/report.html` - visual map for the user
44
+ - `npx -y viberaven init --dry-run` - preview local agent rules
45
+ - `npx -y viberaven clean --plan` - write a non-destructive cleanup plan
46
+
47
+ Free plan: 2 lifetime scans, 6/12 mission map lanes. Pro: 50 scans/month, all 12 lanes.
48
+
49
+ Same VibeRaven account and scan quota as the VS Code extension.
50
+
51
+ Security: the CLI does not read `OPENAI_API_KEY`. Scans use VibeRaven login and the managed API; your model key stays server-side.
52
+
@@ -0,0 +1,17 @@
1
+ <!-- viberaven:agent-rules:start -->
2
+ ## VibeRaven Agent Rules
3
+
4
+ VibeRaven is the Agent Context + Production Gate.
5
+
6
+ - When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
7
+ - Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
8
+ - Read `.viberaven/agent-summary.md` before editing code.
9
+ - Read `.viberaven/launch-playbook.md` before editing code.
10
+ - Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
11
+ - Run `npx -y viberaven --verify` after one fix.
12
+ - Run `npx -y viberaven --strict` before deploy or CI pass.
13
+ - For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
14
+ - Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
15
+ - If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
16
+ <!-- viberaven:agent-rules:end -->
17
+
@@ -0,0 +1,17 @@
1
+ <!-- viberaven:agent-rules:start -->
2
+ ## VibeRaven Agent Rules
3
+
4
+ VibeRaven is the Agent Context + Production Gate.
5
+
6
+ - When production readiness, launch readiness, Vercel, Supabase, auth, database, payments, monitoring, deployment, rate limits, or error handling comes up, run `npx -y viberaven --agent-mode` from the project root.
7
+ - Read `.viberaven/agent-tasklist.md` first, `.viberaven/gate-result.json` for the machine verdict, and `.viberaven/context-map.json` for compact agent context.
8
+ - Read `.viberaven/agent-summary.md` before editing code.
9
+ - Read `.viberaven/launch-playbook.md` before editing code.
10
+ - Use `npx -y viberaven next --json` or `npx -y viberaven prompt --gap <id>` for one focused repo-code fix at a time.
11
+ - Run `npx -y viberaven --verify` after one fix.
12
+ - Run `npx -y viberaven --strict` before deploy or CI pass.
13
+ - For Vercel + Supabase launch checks, run `npx -y viberaven audit --vercel-supabase`.
14
+ - Do not claim provider dashboard work is fixed by repo-code edits. Provider dashboard checks, billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must be completed or verified in the provider dashboard.
15
+ - If VibeRaven prints `LOGIN_URL_READY`, open that URL for the user using the available browser tool or system browser. Tell the user: "I opened VibeRaven sign-in so you can approve access; I will continue after approval." Do not ask for passwords, tokens, cookies, or secrets. Keep the terminal process alive while the user approves.
16
+ <!-- viberaven:agent-rules:end -->
17
+
package/LICENSE DELETED
@@ -1,21 +0,0 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 VibeRaven
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
Binary file