react-dom 19.1.10
- Source
- https://github.com/react/react
- Tag scanned
v19.1.10- Directory
packages/react-dom- Compared with
v19.1.9(0 signals introduced since)- Files
- 217 scanned, 0 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 8 info
- Scan time
- 5.9 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 2 of 2 warn and critical signals; 2 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-15 01:07
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
critical→ info by reviewdynamic-executionpackages/react-dom/src/__tests__/ReactDOMForm-test.js:949:20// eslint-disable-next-line no-new-func result = ; } }likely benign A test in React's DOM form suite evaluates the body of a javascript: action URL with Function() to simulate its behaviour.Reasoning
The Function() call runs the remainder of a javascript: URL string, which is how a test simulates form actions given javascript: URLs. The eslint-disable comment for no-new-func shows the developers intended this use. It sits in a test file, the input comes from test fixtures rather than untrusted runtime data, and nothing in the snippet suggests a dropper or exfiltration. It is still dynamic execution, so the verdict is not certain.
-
info
unicode-surrogatepackages/react-dom/src/events/plugins/__tests__/BeforeInputEventPlugin-test.js:159:38'keypress', , ], }, -
info
unicode-surrogatepackages/react-dom/src/events/plugins/__tests__/BeforeInputEventPlugin-test.js:164:49eventSimulator: simulateEvent, eventSimulatorArgs: , }, -
info
unicode-surrogatepackages/react-dom/src/events/plugins/__tests__/BeforeInputEventPlugin-test.js:293:49.; .; }, }, -
info
unicode-surrogatepackages/react-dom/src/events/plugins/__tests__/BeforeInputEventPlugin-test.js:414:49.; .; }, }, -
info
unicode-surrogatepackages/react-dom/src/events/plugins/__tests__/BeforeInputEventPlugin-test.js:541:49.; .; }, }, -
info
unicode-surrogatepackages/react-dom/src/events/plugins/__tests__/BeforeInputEventPlugin-test.js:676:49.; .; }, }, -
// $FlowFixMe ; }likely benign A Fizz test utility requires a script from a source path inside a try/catch, apparently to load test code dynamically.Reasoning
This is a React test utility that calls require on a script source inside a try block, with a $FlowFixMe comment, so it is a deliberate test harness pattern. The script path comes from the test setup, not from external input, and the catch path only dispatches an error event. The snippet does not show where scriptSrc comes from, but nothing here looks like a supply-chain payload.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&