@viberaven/cli 1.6.3 → 1.6.5

package/README.md

@@ -1,113 +1,67 @@
 # @viberaven/cli
 
-[![npm version](https://img.shields.io/npm/v/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
-[![npm downloads](https://img.shields.io/npm/dw/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
-[![license](https://img.shields.io/npm/l/@viberaven/cli)](https://www.npmjs.com/package/@viberaven/cli)
+A successful deploy does not show whether one user can read another user's rows. VibeRaven reads an AI-built Vercel + Supabase app's repository for missing row level security (RLS), permissive policies and other launch gaps, then writes findings and tasks a coding agent can work through.
 
-<p align="center">
-  <img src="https://raw.githubusercontent.com/ohad6k/VibeRaven/main/assets/banner.png" alt="VibeRaven — AI got your app to demo. VibeRaven gets it to production." width="100%" />
-</p>
+Use a pass before launch or client handoff, after a migration or policy change, or when investigating a production RLS, environment, database connection, service-role or Stripe webhook failure.
 
-VibeRaven is **the Card Table** — a local Studio where your AI-built app is laid out in front of you. Every provider (Supabase, Vercel, Stripe, ...) is a graded trading card in your hand: play a card and its production checks run instantly in chat; a **RAVEN GRADE 10** means that territory is production-ready. Versions are a pile you can pull from, your whole architecture is a region map of cards, and Codex, Claude Code, or Gemini CLI does the actual work — with you controlling how much it's allowed to touch.
+## Start From Your App
 
-## Start the Studio
+Requires Node.js 20 or newer. Run from the app's project root:
 
 ```bash
-npx -y viberaven
-```
-
-That command opens the table:
-
-- **Your hand** — providers as foil cards; click or drop one on the table and its launch checks run in chat, graded 1-10 from repo evidence.
-- **The version pile** — pull a release card to see what changed (real git compare + changelog), view the diff, or ask the agent to explain it.
-- **The region map** — your app as territory: pages, modules, and provider cards connected by routes, every card movable.
-- **Agentic chat** — missions run through your connected CLI, with `ask` / `approve` / `full` access modes and inline approve for risky work.
-- Provider MCP visibility, terminal, and diff views included.
-
-The unscoped `viberaven` package is a small shim that launches this CLI package.
-
-## Agent Connections
-
-Inside the Studio, connect an installed CLI and test it before chat control:
+# Open the local Studio
+npx -y viberaven@1.6.5
 
-- Codex CLI
-- Claude Code
-- Gemini CLI
-
-Installed is not the same as connected. VibeRaven asks the selected CLI to prove it can run in the current repo before using it for real chat work.
-
-## Provider And Release Context
+# Fresh terminal check
+npx -y viberaven@1.6.5 check
+```
 
-Use the Studio side tabs and context chips to attach provider or version context to a chat mission:
+The `viberaven` package launches this CLI. Studio combines findings, provider context and git comparisons. For chat, select an installed/authenticated Codex CLI, Claude Code or Gemini CLI and use **Test connection**. Access modes: `ask`, `approve`, `full`. Stop Studio with Ctrl+C.
 
-- Providers: Supabase, Vercel, GitHub, Stripe, Sentry, PostHog, Clerk, Auth.js, Resend, Upstash.
-- Releases: current and recent git tags, changelog snippets, rollback context, and release comparisons.
-- Architecture: repo and provider boundaries for inspection and planning.
+## Repository Evidence And Tasks
 
-Provider dashboard checks are not cleared by repo-code edits. Billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must still be completed or verified in the provider dashboard or through read-only provider evidence.
+Checks include migration tables without RLS, unrestricted policy conditions such as `USING (true)`, browser-exposed service-role keys, environment names missing from `.env.example` or similar templates, and Stripe handlers without raw-body signature verification.
 
-## Machine And CI Commands
+`check` refreshes `.viberaven/agent-tasklist.md` (tasks and source locations), `gate-result.json` (full verdict), `context-map.json` (agent context) and `gaps/<gapId>.json` without patching app source.
 
-The Studio is the default product surface. These commands remain available for automation and CI:
+`check --json` prints a findings summary and artifact paths. `--json` without `check` runs a fresh scan and prints the full gate object.
 
 ```bash
-npx -y viberaven check --json
-npx -y viberaven --strict --json
-npx -y viberaven actions
-npx -y viberaven --verify --action VR-A1
+npx -y viberaven@1.6.5 check --json
+npx -y viberaven@1.6.5 audit --vercel-supabase --json
+npx -y viberaven@1.6.5 fix --gap <gapId> --dry-run
+npx -y viberaven@1.6.5 init --agents all --dry-run
 ```
 
-For focused work:
-
-```bash
-npx -y viberaven next --json
-npx -y viberaven prompt --gap <id>
-npx -y viberaven audit --vercel-supabase
-```
+Read tasks and source before targeted edits. Preview fixes first. The `rls_disabled` recipe adds an RLS migration without policies: agree before applying, because browser roles lose row access until policies exist. Apply/test through your database workflow; recheck after a batch. Provider actions require provider evidence.
 
-## Legacy Agent Mode
+## Exit Codes And CI
 
-`--agent-mode` is kept for older artifact-first agent workflows:
+`check` returns 0 with no critical blockers, allowing warnings; 1 for critical blockers; 2 for a scan or comparison error. Unrestricted SELECT can be intentional public content and is a default warning. The focused audit returns 1 whenever its status is not `pass`, including warnings.
 
 ```bash
-npx -y viberaven --agent-mode
+# Fail on blockers
+npx -y viberaven@1.6.5 --strict --json
+# Also fail on warnings
+npx -y viberaven@1.6.5 --strict=warning --json
 ```
 
-It writes artifacts such as:
-
-- `.viberaven/agent-tasklist.md`
-- `.viberaven/gate-result.json`
-- `.viberaven/context-map.json`
-- `.viberaven/agent-summary.md`
-- `.viberaven/launch-playbook.md`
+Default `--strict` returns 0 for `clear`/`warning`, 1 for `not_clear`, 2 for `error`, 3 for `unknown` or unavailable results. `--strict=warning` also returns 1 for warnings.
 
-New product work should prefer the Studio and MCP/chat context flow instead of the old tasklist-first loop.
+## Optional Artifact Compatibility Mode
 
-## MCP
-
-Use the MCP package when an agent host supports MCP tools:
+Older integrations can keep the canonical artifact command:
 
 ```bash
-npx -y @viberaven/mcp
+npx -y viberaven --agent-mode
 ```
 
-The MCP server wraps the public CLI and exposes readiness, verification, action, audit, and healing tools without exposing secrets.
+Studio remains the default. MCP hosts use the separate [`@viberaven/mcp`](https://www.npmjs.com/package/@viberaven/mcp) package.
 
-## Development
+## Scope And Evidence
 
-```bash
-npm --prefix packages/cli run typecheck
-npm --prefix packages/cli test -- local-ui/server.test.ts
-npm --prefix packages/cli run build
-```
-
-For a local package publish check, run from this package directory:
-
-```bash
-cd packages/cli
-npm pack --dry-run
-```
+The scan needs no VibeRaven login or API key; npm downloads can need network. It does not query live policies, prove complete permission coverage, run your build or deploy. With RLS off, table grants determine which roles and operations can reach rows. Verify live user access and provider environment, DNS, billing and webhooks separately. A clear result or score is not a security audit.
 
-## License
+The [missing-RLS example](https://ohad6k.github.io/VibeRaven/examples/proof/missing-rls/) and [RLS comparison](https://ohad6k.github.io/VibeRaven/examples/proof/rls-comparison/) retain published **1.6.3** runs. They are maintainer-authored, not new scans or independent endorsement. Comparison databases are local, not hosted Supabase.
 
-MIT
+[Public repository](https://github.com/ohad6k/VibeRaven) | [Agent reference](https://ohad6k.github.io/VibeRaven/llms.txt). License: MIT.

package/dist/cli.js

@@ -8484,8 +8484,9 @@ function readFunctionAttributes(tokens) {
     if (t.value === "security" && next?.kind === "word" && (next.value === "definer" || next.value === "invoker")) {
       out.definer = next.value === "definer";
     }
-    if (t.value === "returns" && next?.kind === "word") {
-      out.returnsTrigger = next.value === "trigger" || next.value === "event_trigger";
+    if (t.value === "returns" && (next?.kind === "word" || next?.kind === "ident")) {
+      const type = next.value;
+      out.returnsTrigger = type === "trigger" || type === "event_trigger";
     }
   }
   return out;
@@ -8613,7 +8614,7 @@ function analyzeRls(replay) {
     }
     if (!table2.rls && (table2.created || table2.disabledLoc)) {
       const where = table2.disabledLoc ?? table2.arrivedLoc ?? table2.created;
-      const risk = "Anyone holding the anon key your frontend ships can read and change every row through the Data API (unless the table's grants were revoked).";
+      const risk = "Without RLS, the Data API does not enforce row restrictions for roles and operations allowed by the table's grants. Verify those grants to determine who can read or change rows.";
       const message = table2.disabledLoc ? `${table2.display} has row level security turned off at ${at(table2.disabledLoc)}. ${risk}` : table2.arrivedLoc ? `${table2.display} is moved into public at ${at(table2.arrivedLoc)} without row level security, and no later migration enables it. ${risk}` : `${table2.display} is created at ${at(table2.created)} and no migration enables row level security on it. ${risk}`;
       missingRls.push({
         id: "rls_disabled",
@@ -9439,7 +9440,7 @@ function buildRlsCheck(replay) {
       id: "supabase-rls-policy-proof",
       title: "Supabase RLS policy proof",
       status: "needs_work",
-      summary: `${plural(analysis.missingRls.length, "public table")} without row level security: ${names}. Anyone holding the anon key your frontend ships can read and change those rows through the Data API.`,
+      summary: `${plural(analysis.missingRls.length, "public table")} without row level security: ${names}. The Data API does not enforce row restrictions for roles and operations allowed by the table's grants. Verify those grants to determine who can read or change rows.`,
       evidence: findingEvidence(analysis.missingRls),
       findings
     };
@@ -15022,7 +15023,7 @@ var VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    VERSION = "1.6.3";
+    VERSION = "1.6.5";
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viberaven/cli",
-  "version": "1.6.3",
+  "version": "1.6.5",
   "description": "VibeRaven CLI and local Studio: Supabase RLS and security check for AI-built Vercel + Supabase apps, with an agent task list and fix prompts.",
   "license": "MIT",
   "author": "VibeRaven",