npm / react-dom / 0.0.0-experimental-ba39b32a-20261019

react-dom 0.0.0-experimental-ba39b32a-20261019

Source
https://github.com/react/react
Commit scanned
ba39b32a467e (recorded by npm)
Directory
packages/react-dom (only this part of the repository was scanned)
Compared with
nothing (first release scanned in full)
Files
227 scanned, 0 skipped (binary, oversized, or unrecognised)
Signals
0 critical · 0 warn · 8 info
Scan time
6.3 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-20 10:45

Signals

Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.

  1. info critical → info by review dynamic-execution packages/react-dom/src/__tests__/ReactDOMForm-test.js:963:20

    `Function(...)` called with a non-literal body (ast pass, confidence 0.75)

              // eslint-disable-next-line no-new-func
              result = Function(action.slice(11))();
            }
          } catch (x) {
    likely benign LLM, confidence 0.85 Test code that evaluates a javascript: form action body via Function() to simulate browser behavior.
    Reasoning

    The snippet is inside a React DOM form test. The Function() call evaluates the body of a javascript: action URL, which simulates how a browser would run such an action, and the eslint-disable comment for no-new-func shows the call was deliberate. The input comes from test fixtures rather than untrusted input, and the surrounding try/catch matches test assertions about errors. This is a test harness reproducing browser behavior, not a dropper. The remaining doubt is that a non-literal Function() call is inherently risky if this file ever received external data.

  2. surrogate pair \uD83D\uDE0A (non-scalar Unicode codepoints in string literal) (token pass, confidence 0.70)

            'keypress',
            {which: keyCode('X'), char: '\uD83D\uDE0A'},
          ],
        },
  3. surrogate pair \uD83D\uDE0A (non-scalar Unicode codepoints in string literal) (token pass, confidence 0.70)

          eventSimulator: simulateEvent,
          eventSimulatorArgs: ['textInput', {data: '\uD83D\uDE0A'}],
        },
        {
  4. surrogate pair \uD83D\uDE0A (non-scalar Unicode codepoints in string literal) (token pass, confidence 0.70)

                expect(beforeInputEvent.type).toBe('beforeinput');
                expect(beforeInputEvent.data).toBe('\uD83D\uDE0A');
              },
            },
  5. surrogate pair \uD83D\uDE0A (non-scalar Unicode codepoints in string literal) (token pass, confidence 0.70)

                expect(beforeInputEvent.type).toBe('beforeinput');
                expect(beforeInputEvent.data).toBe('\uD83D\uDE0A');
              },
            },
  6. surrogate pair \uD83D\uDE0A (non-scalar Unicode codepoints in string literal) (token pass, confidence 0.70)

                expect(beforeInputEvent.type).toBe('beforeinput');
                expect(beforeInputEvent.data).toBe('\uD83D\uDE0A');
              },
            },
  7. surrogate pair \uD83D\uDE0A (non-scalar Unicode codepoints in string literal) (token pass, confidence 0.70)

                expect(beforeInputEvent.type).toBe('beforeinput');
                expect(beforeInputEvent.data).toBe('\uD83D\uDE0A');
              },
            },
  8. info warn → info by review dynamic-import packages/react-dom/src/test-utils/FizzTestUtils.js:99:7

    `require` called with a non-literal specifier (ast pass, confidence 0.60)

          // $FlowFixMe[unsupported-syntax]
          require(scriptSrc);
        } catch (x) {
          const event = new window.ErrorEvent('error', {error: x});
    likely benign LLM, confidence 0.85 Test helper that dynamically requires a script path and reports load errors via an ErrorEvent.
    Reasoning

    This is a test utility that requires a script source inside a try/catch and reports failures by dispatching a synthetic ErrorEvent on the window. The Flow suppression comment indicates an intentional dynamic require. The specifier is a test-controlled script path, not attacker-supplied data, and nothing in the snippet suggests exfiltration or a remote fetch. The residual doubt is that the scriptSrc origin is not visible in this snippet.

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.

cargo install disclude --version 4.0.0
git clone https://github.com/react/react react && cd react
git checkout ba39b32a467ea462ffb06db242da2bfc09e23af8
disclude scan --severity info packages/react-dom