Find the Node 24 risks hiding in your Actions workflow.
GitHub switched JavaScript actions to Node 24 by default on June 16. Paste or open workflow YAML to inventory remote actions and flag old local runtimes, temporary opt-outs, and runner risks. Your file contents stay in this browser.
Scan a workflow or action manifest
Paste YAML or choose one or more .yml/.yaml files. No repository login, token, or upload. Anonymous page, scan, report-download, and checkout-click counts are recorded; file names and contents are not.
Remote action manifests are resolved through a narrow Good AiDeas proxy that accepts only public GitHub action coordinates. Workflow contents are never sent.
Why this exists now
GitHub’s changelog says Node 20 reached end of life in April 2026, Node 24 became the default action runtime on June 16, and the temporary Node 20 opt-out lasts only until runner removal later in fall 2026. Maintainers are still opening migration issues and asking whether their dependencies are ready.
GitHub’s Node 20 deprecation notice · Example maintainer migration issue
Boundary: This is a static preflight, not proof that a workflow will pass. Run the workflow under Node 24 and review each dependency’s release notes before changing production automation.