@withone/cli - npm Package Compare versions

Comparing version 1.25.0 to 1.26.0

dist/flow-runner-3DCROTPW.js

+import {
+  FlowRunner,
+  collectStepTypes,
+  flowRequiresBash,
+  flowUsesCodeModules,
+  getFlowRootDir,
+  listFlows,
+  loadFlow,
+  loadFlowWithMeta,
+  resolveFlowPath,
+  saveFlow,
+  summarizeFlowInputs,
+  walkSteps
+} from "./chunk-ZOIXA7MV.js";
+export {
+  FlowRunner,
+  collectStepTypes,
+  flowRequiresBash,
+  flowUsesCodeModules,
+  getFlowRootDir,
+  listFlows,
+  loadFlow,
+  loadFlowWithMeta,
+  resolveFlowPath,
+  saveFlow,
+  summarizeFlowInputs,
+  walkSteps
+};

package.json

 {
   "name": "@withone/cli",
-  "version": "1.25.0",
+  "version": "1.26.0",
   "description": "CLI for managing One",
@@ -5,0 +5,0 @@ "type": "module",

skills/one/references/flows.md

@@ -189,5 +189,25 @@ # One Workflows — Multi-Step API Workflows
 | `connection` | `{ "platform": "gmail" }` — enables auto-resolution |
+| `enum` | Array of allowed values; rejected if input doesn't match (post-coercion) |
 
 Connection inputs with a `connection` field auto-resolve if the user has exactly one connection for that platform.
 
+**Validation, coercion, and enums.** At flow start the engine validates every declared input:
+
+1. **Required check** — `required: true` (the default) inputs without a value or `default` cause `Missing required input: "X"`.
+2. **Type coercion** — narrow, bidirectional fixes only:
+   - `number`: numeric strings (`"5"`) become `5`. Non-numeric strings throw.
+   - `boolean`: `"true"`/`"1"`/`1` → `true`; `"false"`/`"0"`/`0` → `false`. Anything else throws.
+   - `array` / `object`: JSON strings are parsed. Non-JSON throws.
+   - `string`: anything else is `String(value)`-coerced.
+3. **Enum check** — if `enum` is set, the (coerced) value must be `===` one of the allowed entries. Errors quote both the allowed list and the actual value.
+
+This eliminates the per-flow `if (!$.input.x) throw ...` boilerplate. Errors look like:
+
+```
+Input "tier" must be a number, got string ("lots")
+Input "stage" must be one of ["pre_seed","seed","series_a"], got "ipo"
+```
+
+The same checks run when a step calls a sub-flow, so type/enum guarantees hold across the call boundary.
+
 ## Selector Syntax
@@ -194,0 +214,0 @@

dist/flow-runner-MXRNWG4Y.js

-import {
-  FlowRunner,
-  collectStepTypes,
-  flowRequiresBash,
-  flowUsesCodeModules,
-  getFlowRootDir,
-  listFlows,
-  loadFlow,
-  loadFlowWithMeta,
-  resolveFlowPath,
-  saveFlow,
-  summarizeFlowInputs,
-  walkSteps
-} from "./chunk-ONGJ2QKB.js";
-export {
-  FlowRunner,
-  collectStepTypes,
-  flowRequiresBash,
-  flowUsesCodeModules,
-  getFlowRootDir,
-  listFlows,
-  loadFlow,
-  loadFlowWithMeta,
-  resolveFlowPath,
-  saveFlow,
-  summarizeFlowInputs,
-  walkSteps
-};

New alerts

Network access

Supply chain risk

This module accesses the network.

Found 1 instance in 1 package

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Found 1 instance in 1 package

Uses eval

Supply chain risk

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Found 1 instance in 1 package

Debug access

Supply chain risk

Uses debug, reflection and dynamic code execution features.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 6 instances in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Found 1 instance in 1 package

Fixed alerts

Network access

Supply chain risk

This module accesses the network.

Found 1 instance in 1 package

Shell access

Supply chain risk

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Found 1 instance in 1 package

Uses eval

Supply chain risk

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Found 1 instance in 1 package

Debug access

Supply chain risk

Uses debug, reflection and dynamic code execution features.

Found 1 instance in 1 package

Environment variable access

Supply chain risk

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Found 6 instances in 1 package

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

Found 1 instance in 1 package

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

Found 1 instance in 1 package

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

315686

1.15%

Lines of code

6835

0.93%

No dependency changes