codex-workflows 0.2.0 → 0.2.1

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.
@@ -14,17 +14,17 @@ These patterns have low false-positive rates and are detectable through grep or
14
14
 
15
15
  ### SQL String Concatenation
16
16
  - SQL statements constructed through string concatenation or interpolation with variables
17
- - Detection approach: search for SQL keywords (`SELECT`, `INSERT`, `UPDATE`, `DELETE`) combined with string concatenation operators or template literals containing variable references
17
+ - Detection approach: search for SQL keywords (`SELECT`, `INSERT`, `UPDATE`, `DELETE`) combined with string concatenation operators or string interpolation containing variable references
18
18
 
19
19
  ### Dynamic Code Execution
20
- - Use of `eval()`, `Function()`, `exec()`, `compile()` with dynamic input
21
- - Dynamic import or require with variable paths
22
- - Detection approach: search for these function calls where the argument is not a static literal
20
+ - Use of dynamic code execution functions (e.g., `eval`, `exec`) with non-static input
21
+ - Dynamic module loading with variable paths
22
+ - Detection approach: search for dynamic code execution or module loading calls where the argument is not a static literal
23
23
 
24
24
  ### Insecure Deserialization
25
- - `pickle.loads()`, `yaml.load()` without SafeLoader, `marshal.loads()` with untrusted input
26
- - `JSON.parse()` followed by direct use in `eval()` or `Function()`
27
- - Detection approach: search for deserialization calls that accept external input without safe loader configuration
25
+ - Deserialization of untrusted input using unsafe loaders or formats that allow arbitrary object construction (e.g., native serialization, YAML without safe loader)
26
+ - Parsed data passed directly into dynamic code execution
27
+ - Detection approach: search for deserialization calls that accept external input without safe loader or type-restricted configuration
28
28
 
29
29
  ### Path Traversal
30
30
  - File system paths constructed from user-supplied input without sanitization
@@ -179,12 +179,12 @@ No Ripple Effect:
179
179
 
180
180
  ```yaml
181
181
  Input:
182
- Type: [Type/interface definition]
182
+ Type: [Data shape, contract, or schema]
183
183
  Preconditions: [Required items, format constraints]
184
184
  Validation: [Validation method]
185
185
 
186
186
  Output:
187
- Type: [Type/interface definition]
187
+ Type: [Data shape, contract, or schema]
188
188
  Guarantees: [Conditions that must always be met]
189
189
  On Error: [Exception/null/default value]
190
190
 
@@ -78,7 +78,7 @@ Document modification and solution proposals are out of scope for this agent.
78
78
  | Implementation | 1 | Direct code implementing the claim |
79
79
  | Tests | 2 | Test cases verifying expected behavior |
80
80
  | Config | 3 | Configuration files, environment variables |
81
- | Types | 4 | Type definitions, interfaces, schemas |
81
+ | Types & Contracts | 4 | Type definitions, schemas, API contracts |
82
82
 
83
83
  MUST collect from at least 2 sources before classifying. Single-source findings MUST be marked with lower confidence.
84
84
 
@@ -185,19 +185,17 @@ ENFORCEMENT: sync_status MUST be one of: CONFLICTS_FOUND | NO_CONFLICTS | SKIPPE
185
185
 
186
186
  ### Type Definition Mismatch
187
187
  ```
188
- // Source Design Doc
189
- interface User {
188
+ Source Design Doc:
189
+ User
190
190
  id: string
191
191
  email: string
192
- role: 'admin' | 'user'
193
- }
192
+ role: admin | user
194
193
 
195
- // Other Design Doc (conflict)
196
- interface User {
197
- id: number // different type
194
+ Other Design Doc (conflict):
195
+ User
196
+ id: number # different type
198
197
  email: string
199
- userRole: string // different property name and type
200
- }
198
+ userRole: string # different property name and type
201
199
  ```
202
200
 
203
201
  ### Numeric Parameter Mismatch
@@ -221,7 +221,7 @@ MUST follow these principles to maintain high-quality code:
221
221
 
222
222
  **Required Fix Approaches**:
223
223
  - Test failures → Fix implementation or test logic to pass genuinely
224
- - Type errors → Add proper types or type guards with explicit typing
224
+ - Type/contract errors → Fix type mismatches or interface/contract violations at their source
225
225
  - Errors → Log with context or propagate with error chain
226
226
  - Safety warnings → Address root cause directly
227
227
 
@@ -87,7 +87,7 @@ Explore the codebase from both user-value and technical perspectives simultaneou
87
87
  | Test Files | 2 | User-value | E2E tests, integration tests (often named by feature) |
88
88
  | User-facing Components | 3 | User-value | Pages, screens, major UI components |
89
89
  | Module Structure | 4 | Technical | Service classes, controllers, repositories |
90
- | Interface Definitions | 5 | Technical | Public APIs, exported functions, type definitions |
90
+ | Public Interfaces | 5 | Technical | Public APIs, exported functions, data shapes/schemas |
91
91
  | Dependency Graph | 6 | Technical | Import/export relationships, DI configurations |
92
92
  | Directory Structure | 7 | Both | Feature-based directories, domain directories |
93
93
  | Data Flow | 8 | Technical | Data transformations, state management |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "codex-workflows",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "description": "Task-oriented agentic coding framework for OpenAI Codex CLI — skills, recipes, and subagents for structured development workflows",
5
5
  "license": "MIT",
6
6
  "author": "Shinsuke Kagawa",