Skip to content
CI

feat(engine): security hardening (path containment, YAML limits, reserved IDs) #48

Sign in to view logs

feat(engine): security hardening (path containment, YAML limits, reserved IDs)

feat(engine): security hardening (path containment, YAML limits, reserved IDs) #48

Triggered via pull request March 19, 2026 00:17
@albertgwoalbertgwo
opened #9
feat/engine-pr0a-security-hardening
Status Failure
Total duration 27s
Artifacts –

ci.yml

on: pull_request
Build, Test & Lint
24s
Build, Test & Lint
Playwright E2E
0s
Playwright E2E
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Build, Test & Lint
Process completed with exit code 2.
Build, Test & Lint
@ruminaider/flowprint-schema#typecheck: command (/home/runner/work/flowprint/flowprint/packages/schema) /home/runner/setup-pnpm/node_modules/.bin/pnpm run typecheck exited (2)
Build, Test & Lint
Element implicitly has an 'any' type because expression of type '"trigger" | "action" | "switch" | "parallel" | "wait" | "error" | "terminal"' can't be used to index type '{ action: number; switch: number; parallel: number; wait: number; error: number; terminal: number; }'.
Build, Test & Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/