@cantinasecurity/apex-cli 0.1.13 → 0.1.14

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.
@@ -13,6 +13,8 @@ This skill is bundled with Apex CLI and can be installed into the current reposi
13
13
 
14
14
  Use Apex through the MCP server when the `apex-*` tools are available.
15
15
 
16
+ For on-prem or other non-default Apex hosts, make sure the CLI or MCP server runs with `APEX_BASE_URL` set to the external HTTPS Bedrock origin before auth or provider connection flows.
17
+
16
18
  Recommended workflow:
17
19
 
18
20
  1. Start with `apex-auth-status`.
@@ -6,7 +6,7 @@
6
6
  },
7
7
  "metadata": {
8
8
  "description": "Cantina agent plugins for security review workflows.",
9
- "version": "0.1.13"
9
+ "version": "0.1.14"
10
10
  },
11
11
  "plugins": [
12
12
  {
@@ -14,10 +14,10 @@
14
14
  "source": {
15
15
  "source": "npm",
16
16
  "package": "@cantinasecurity/apex-cli",
17
- "version": "0.1.13"
17
+ "version": "0.1.14"
18
18
  },
19
19
  "description": "Run Apex security scans and review findings from Claude Code.",
20
- "version": "0.1.13",
20
+ "version": "0.1.14",
21
21
  "author": {
22
22
  "name": "Cantina",
23
23
  "email": "support@cantina.xyz"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "apex-cli",
3
- "version": "0.1.13",
3
+ "version": "0.1.14",
4
4
  "description": "Run Apex security scans and review findings from Claude Code.",
5
5
  "author": {
6
6
  "name": "Cantina",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "apex-cli",
3
- "version": "0.1.13",
3
+ "version": "0.1.14",
4
4
  "description": "Run Apex security scans and review findings from Codex.",
5
5
  "author": {
6
6
  "name": "Cantina",
package/.mcp.claude.json CHANGED
@@ -5,7 +5,7 @@
5
5
  "args": [
6
6
  "-y",
7
7
  "-p",
8
- "@cantinasecurity/apex-cli@0.1.13",
8
+ "@cantinasecurity/apex-cli@0.1.14",
9
9
  "apex-mcp"
10
10
  ],
11
11
  "env": {
package/.mcp.codex.json CHANGED
@@ -4,7 +4,7 @@
4
4
  "args": [
5
5
  "-y",
6
6
  "-p",
7
- "@cantinasecurity/apex-cli@0.1.13",
7
+ "@cantinasecurity/apex-cli@0.1.14",
8
8
  "apex-mcp"
9
9
  ],
10
10
  "env": {
package/MARKETPLACE.md CHANGED
@@ -13,7 +13,7 @@ This package is prepared as both a Claude Code plugin and a Codex plugin. The pu
13
13
  The plugin MCP configs launch the pinned npm CLI package with:
14
14
 
15
15
  ```bash
16
- npx -y -p @cantinasecurity/apex-cli@0.1.13 apex-mcp
16
+ npx -y -p @cantinasecurity/apex-cli@0.1.14 apex-mcp
17
17
  ```
18
18
 
19
19
  That keeps marketplace installs independent of a user's global `apex` install.
package/README.md CHANGED
@@ -74,10 +74,13 @@ pnpm apex
74
74
 
75
75
  By default, the CLI targets `https://ai.cantina.xyz/`.
76
76
 
77
- Use `APEX_BASE_URL` only when testing against a non-production Apex host:
77
+ Use `APEX_BASE_URL` only when targeting a non-default Apex host. For on-prem deployments,
78
+ set it to the same external HTTPS Bedrock origin configured as `ONPREM_PUBLIC_BASE_URL`;
79
+ browser handoffs such as `apex connect github` and `apex-connect-provider` need that
80
+ public origin for GitHub callback and success redirects.
78
81
 
79
82
  ```bash
80
- APEX_BASE_URL=https://preview.cantina.xyz pnpm apex
83
+ APEX_BASE_URL=https://bedrock.customer.example pnpm apex
81
84
  ```
82
85
 
83
86
  ## Interactive Shell
@@ -347,7 +350,7 @@ Telemetry event posts do not include bearer tokens. The telemetry endpoint is `P
347
350
  {
348
351
  "schemaVersion": 1,
349
352
  "event": "apex.invocation.completed",
350
- "cliVersion": "0.1.13",
353
+ "cliVersion": "0.1.14",
351
354
  "invocation": {
352
355
  "surface": "mcp",
353
356
  "command": "apex-scan",
@@ -378,7 +381,7 @@ The npm package also includes marketplace-ready plugin artifacts:
378
381
  - `.claude-plugin/plugin.json` and `.mcp.claude.json` for Claude Code plugin installs
379
382
  - `.claude-plugin/marketplace.json` for a Claude marketplace entry backed by the public npm package
380
383
 
381
- These plugin installs launch the pinned npm package with `npx -y -p @cantinasecurity/apex-cli@0.1.13 apex-mcp`, so users do not need to install `apex` globally before enabling the plugin.
384
+ These plugin installs launch the pinned npm package with `npx -y -p @cantinasecurity/apex-cli@0.1.14 apex-mcp`, so users do not need to install `apex` globally before enabling the plugin.
382
385
 
383
386
  The repository also includes `.agents/plugins/marketplace.json` for local Codex marketplace testing from a checkout.
384
387
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cantinasecurity/apex-cli",
3
- "version": "0.1.13",
3
+ "version": "0.1.14",
4
4
  "description": "Standalone CLI and MCP server for Apex.",
5
5
  "private": false,
6
6
  "type": "module",
@@ -11,6 +11,8 @@ Prefer the Apex MCP tools over running `apex` in the shell when the server is av
11
11
 
12
12
  `apex setup codex` configures the MCP server with client attribution so Apex can distinguish Codex MCP usage from direct CLI usage. Users can inspect or disable anonymous local usage telemetry with `apex telemetry status` and `apex telemetry disable`.
13
13
 
14
+ For on-prem or other non-default Apex hosts, make sure the MCP server runs with `APEX_BASE_URL` set to the external HTTPS Bedrock origin before auth or provider connection flows.
15
+
14
16
  Workflow:
15
17
 
16
18
  1. Start with `apex-auth-status`.