npm / react / 0.0.0-experimental-99c106c4-20261014
react 0.0.0-experimental-99c106c4-20261014
- Source
- https://github.com/react/react
- Commit scanned
99c106c43439- Directory
packages/react- Compared with
997f52fbb30e(0 signals introduced since)- Files
- 84 scanned, 2 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 4 info
- Scan time
- 3.5 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 4 of 4 warn and critical signals; 4 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-15 12:41
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
likely benign Error message string in React's lazy implementation split across concatenation to keep the word 'import' from being parsed as a dependency.
Reasoning
This is React's lazy() module splitting a string literal to avoid bundlers parsing a literal 'import(' inside an error message. The comment in the adjacent finding confirms the intent. Benign.
-
// Break up imports to avoid accidentally parsing them as dependencies. 'const MyComponent = lazy(() => imp' + "ort('./MyComponent'))\n\n" + 'Did you accidentally put curly braces around the import?',likely benign Example code string in a React developer warning split across concatenation to avoid bundler dependency parsing.Reasoning
Same pattern: developer-facing error text containing example code, split so bundlers do not treat the example import as a real dependency. The source comment states this explicitly. No execution or hidden payload.
-
likely benign Second copy of the lazy() dynamic import error message split across concatenation.
Reasoning
Duplicate of the error message in the earlier block of the same React lazy module, with the same benign purpose of a readable warning string.
-
// Break up imports to avoid accidentally parsing them as dependencies. 'const MyComponent = lazy(() => imp' + "ort('./MyComponent'))", moduleObject,likely benign Example code in a console error message split across concatenation in React's lazy module.Reasoning
Same benign pattern as the other findings: an example snippet in a console error, split to avoid bundler import parsing, with an explanatory comment. Token-pass string-concat signals on literal text are a known false-positive class.
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.
&&