@cipherstash/stack 0.12.0 → 0.13.0

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @cipherstash/stack
 
+## 0.13.0
+
+### Minor Changes
+
+- 068f820: Release the consolidated CipherStash CLI npm package.
+
 ## 0.12.0
 
 ### Minor Changes

package/README.md

@@ -47,7 +47,7 @@ pnpm add @cipherstash/stack
 ### 1. Initialize and authenticate your project
 
 ```bash
-npx stash init
+npx @cipherstash/cli init
 ```
 
 The wizard will authenticate you, walk you through choosing a database connection method, build an encryption schema, and install the required dependencies.
@@ -438,25 +438,25 @@ await secrets.delete("DATABASE_URL")
 
 ## CLI Reference
 
-The `stash` CLI is bundled with the package and available after install.
+The CLI is available via `npx @cipherstash/cli` after install.
 
-### `stash auth`
+### `npx @cipherstash/cli auth`
 
 Authenticate with CipherStash.
 
 ```bash
-npx stash auth login
+npx @cipherstash/cli auth login
 ```
 
 This runs the device code flow: it opens your browser, you confirm the code, and a token is saved to `~/.cipherstash/auth.json`. No environment variables or credentials files are needed for local development.
 
-### `stash init`
+### `npx @cipherstash/cli init`
 
 Initialize CipherStash for your project with an interactive wizard.
 
 ```bash
-npx stash init
-npx stash init --supabase
+npx @cipherstash/cli init
+npx @cipherstash/cli init --supabase
 ```
 
 The wizard will:
@@ -464,31 +464,31 @@ The wizard will:
 2. Bind your device to the default Keyset
 3. Choose your database connection method (Drizzle ORM, Supabase JS, Prisma, or Raw SQL)
 4. Build an encryption schema interactively or use a placeholder, then generate the encryption client file
-5. Install `@cipherstash/stack-forge` as a dev dependency for database tooling
+5. Install `@cipherstash/cli` as a dev dependency for database tooling
 
-After `stash init`, run `npx stash-forge setup` to configure your database.
+After init, run `npx @cipherstash/cli db setup` to configure your database.
 
 | Flag | Description |
 |------|-------------|
 | `--supabase` | Use Supabase-specific setup flow |
 
-### `stash secrets`
+### `npx @cipherstash/cli secrets`
 
 Manage encrypted secrets from the terminal.
 
 ```bash
-npx stash secrets set  -name DATABASE_URL -value "postgres://..." -environment production
-npx stash secrets get  -name DATABASE_URL -environment production
-npx stash secrets list -environment production
-npx stash secrets delete -name DATABASE_URL -environment production
+npx @cipherstash/cli secrets set  -name DATABASE_URL -value "postgres://..." -environment production
+npx @cipherstash/cli secrets get  -name DATABASE_URL -environment production
+npx @cipherstash/cli secrets list -environment production
+npx @cipherstash/cli secrets delete -name DATABASE_URL -environment production
 ```
 
 | Command | Flags | Aliases | Description |
 |-----|----|-----|-------|
-| `stash secrets set` | `-name`, `-value`, `-environment` | `-n`, `-V`, `-e` | Encrypt and store a secret |
-| `stash secrets get` | `-name`, `-environment` | `-n`, `-e` | Retrieve and decrypt a secret |
-| `stash secrets list` | `-environment` | `-e` | List all secret names in an environment |
-| `stash secrets delete` | `-name`, `-environment`, `-yes` | `-n`, `-e`, `-y` | Delete a secret (prompts for confirmation unless `-yes`) |
+| `npx @cipherstash/cli secrets set` | `-name`, `-value`, `-environment` | `-n`, `-V`, `-e` | Encrypt and store a secret |
+| `npx @cipherstash/cli secrets get` | `-name`, `-environment` | `-n`, `-e` | Retrieve and decrypt a secret |
+| `npx @cipherstash/cli secrets list` | `-environment` | `-e` | List all secret names in an environment |
+| `npx @cipherstash/cli secrets delete` | `-name`, `-environment`, `-yes` | `-n`, `-e`, `-y` | Delete a secret (prompts for confirmation unless `-yes`) |
 
 ## Configuration
 
@@ -676,7 +676,7 @@ If you are migrating from `@cipherstash/protect`, the following table maps the o
 | `csColumn(name)` | `encryptedColumn(name)` | `@cipherstash/stack/schema` |
 | `import { LockContext } from "@cipherstash/protect/identify"` | `import { LockContext } from "@cipherstash/stack/identity"` | `@cipherstash/stack/identity` |
 | N/A | `Secrets` class | `@cipherstash/stack/secrets` |
-| N/A | `stash` CLI | `npx stash` |
+| N/A | CLI | `npx @cipherstash/cli` |
 
 All method signatures on the encryption client (`encrypt`, `decrypt`, `encryptModel`, etc.) remain the same. The `Result` pattern (`data` / `failure`) is unchanged.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cipherstash/stack",
-  "version": "0.12.0",
+  "version": "0.13.0",
   "description": "CipherStash Stack for TypeScript and JavaScript",
   "keywords": [
     "encrypted",
@@ -27,9 +27,6 @@
     "CHANGELOG.md"
   ],
   "type": "module",
-  "bin": {
-    "stash": "./dist/bin/stash.js"
-  },
   "main": "./dist/index.cjs",
   "module": "./dist/index.js",
   "sideEffects": false,
@@ -200,8 +197,7 @@
   },
   "dependencies": {
     "@byteslice/result": "0.2.0",
-    "@cipherstash/auth": "0.34.2",
-    "@cipherstash/protect-ffi": "0.21.0",
+    "@cipherstash/protect-ffi": "0.21.2",
     "evlog": "1.9.0",
     "uuid": "13.0.0",
     "zod": "3.24.2"
@@ -223,7 +219,6 @@
   },
   "scripts": {
     "build": "tsup",
-    "postbuild": "chmod +x ./dist/bin/stash.js",
     "dev": "tsup --watch",
     "test": "vitest run",
     "release": "tsup"