rolldown 1.2.14
- Source
- https://github.com/rolldown/rolldown
- Tag scanned
v1.2.14- Directory
packages/rolldown- Compared with
v1.2.13(11 signals introduced since)- Files
- 1736 scanned, 78 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 86 info
- Scan time
- 51.4 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 65 of 65 warn and critical signals; 65 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 21:04
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/preserve-entry-signatures.test.ts:136:24new in this release.; const main = await ; .; .;likely benign Test imports generated chunk via data URI to check entry signature preservation.Reasoning
Test imports the bundler's generated chunk as a data URI to verify entry exports; the code under test is produced by the build in the same test.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:39:19new in this releaseformat === 'es' ? await :likely benign Test helper dynamically imports a data: URI containing bundler-generated ES module code.Reasoning
The data: URI import evaluates bundler output generated in the same test. The code comes from bundle.generate() inside a test fixture, not from an external or attacker-controlled source, and the pattern is a standard way to load ES module output in a test harness.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:75:31new in this releaseconst = ; const namespace = await ; .; .;likely benign Test loads generated ES module chunk via data: URI to check namespace exports.Reasoning
Same pattern: chunk.code from a local rollup-style bundle is loaded via a data: URI so the test can assert on its exports. The snippet shows assertions on the namespace, consistent with testing module shim behavior.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:121:31new in this releaseconst = ; const namespace = await ; .; .;likely benign Test imports bundled output as data URI and asserts on namespace properties.Reasoning
The import evaluates bundler output produced in the test itself, and the following expectations check namespace shape. No sign of hidden payload or external fetch.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:143:29new in this releaseconst = ; const namespace = await ; .;likely benign Test evaluates generated module code via data: URI and checks warning codes.Reasoning
The data: URI carries code generated by bundle.generate in the same test file. The surrounding assertions verify warnings and keys, which is typical of bundler test suites.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:219:31new in this releaseconst = ; const namespace = await ; .; .;likely benign Test dynamically imports generated chunk to verify export keys and warnings.Reasoning
Dynamic import of locally generated bundle code in a test, followed by assertions on keys and warnings. This is expected test scaffolding.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:238:29new in this releaseconst = ; const namespace = await ; .; .;likely benign Test evaluates generated module via data: URI to assert a warning code.Reasoning
Same test-harness pattern: generated module code is evaluated through a data: URI to check that an IMPORT_IS_UNDEFINED warning is produced.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:255:29new in this releaseconst = ; const namespace = await ; .; .;likely benign Test loads generated module via data: URI and compares namespace spreads.Reasoning
The import evaluates bundler output built in the test. The assertions compare spread namespace objects, which is ordinary test verification of export shims.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:288:29new in this releaseconst = ; const namespace = await ; .; .;likely benign Test imports generated bundle via data: URI and checks keys and warnings.Reasoning
Dynamic import of locally built bundle code within a behavior test. Expectations check keys and warnings only, with no external data or execution side effects.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-interface.test.ts:303:29new in this releaseconst = ; const namespace = await ; .; .;likely benign Test loads generated module via data: URI and asserts exported values.Reasoning
The data: URI wraps code produced by the test's own bundle.generate call. The assertions check exported values, consistent with normal testing of a bundler plugin.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-names.test.ts:39:29new in this releaselikely benign Test imports generated dependency code via data: URI in an ES-format branch.Reasoning
Same harness pattern in a sibling test file: dep.code from a local bundle is imported as a data: URI in an ES-format branch, with a CommonJS-style fallback. This is a test for export-name shimming, not a dropper.
-
likely benign Build script dynamically imports a runtime base file to enumerate helper names.
Reasoning
Dynamic import of a path derived from a build-time base input file via pathToFileURL in a build script; this is a bundler config helper loading its own runtime entry, a common legitimate pattern.
-
likely benign NAPI binding loader requires an override library path from an environment variable.
Reasoning
require of an environment-variable path (NAPI_RS_NATIVE_LIBRARY_PATH) is a documented override for native binding loading; env-controlled but a standard developer knob, with comments explaining intent.
-
info
critical→ info by reviewdynamic-executionpackages/rolldown/src/options/docs/checks-eval.md:6:1const code = 'console.log("Hello")'; ; // This triggers the warningdismissed Documentation snippet showing an eval call that the scanner warns about.Reasoning
This is a markdown documentation example demonstrating what the eval check flags; the code is illustrative and inert, not executable project code.
-
pluginInfos.likely benign Parallel plugin worker imports plugin modules from configured file URLs.Reasoning
Loads plugin modules from a configured fileUrl in a bundler's parallel plugin worker; plugin loading by design imports user-specified modules, so this is expected behavior.
-
likely benign Config loader dynamically imports a transpiled config file and cleans it up.
Reasoning
Config loader imports a temporary transpiled config file via file URL and then deletes it; standard config-loading pattern.
-
// Runtimes without Module-hook support (e.g. Bun/Deno) const mod = await ; return mod.; }likely benign Config loader imports config via URL with timestamp cache-busting.Reasoning
Imports a config URL with a cache-busting timestamp query for runtimes lacking module hooks; a legitimate config reload technique.
-
)likely benign Config loader dynamically imports a resolved config file path.Reasoning
Imports the resolved config file path for a supported config extension; expected behavior for a bundler loading its own config.
-
module.exports = ;likely benign WebContainer fallback re-exports a binding loaded via a variable path.Reasoning
Fallback module re-exports a binding resolved from a bindingEntry variable, a typical native binding fallback in a package; the variable is internal, though the path origin is not shown.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/arbitrary-import-names.test.ts:92:31return; const namespace = await ; .; }likely benign Test imports generated chunk code via a data URI to check export names.Reasoning
Test harness imports bundler output as a data URI to verify export names; the data URI contains the build's own generated chunk code, not attacker payload.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/behaviors/dependency-path-escaping.test.ts:70:72const ; define. = true;likely benign Test AMD define shim requires dependency ids.Reasoning
AMD define shim in a test resolves ids with require for a path-escaping behavior test; a test fixture mimicking AMD loaders, not malicious.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/behaviors/inline-common-chunks/run-root.mjs:44:29likely benign Test runner dynamically imports a generated bundle file.Reasoning
Test runner imports a file it generated from a known path to check inlined chunk exports; ordinary test harness behavior.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/mangle-properties.test.ts:120:11likely benign Test executes generated chunk code via data URI to verify mangling.Reasoning
Test imports the bundler's own generated chunk as a data URI to verify property mangling results; test scaffolding, not an attack.
-
info
critical→ info by reviewdata-uri-importpackages/rolldown/tests/behaviors/shim-missing-export-names.test.ts:99:31likely benign Test helper that loads rolled-up ES chunk code via a data: URI dynamic import.Reasoning
The data: URI import is used to evaluate bundler output chunk code in a test harness for ES format shim behavior. It is test-only code evaluating generated bundle output, so the flagged dynamic execution is a legitimate testing technique, though it does execute code from a string.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/dev/dev-lazy-compile.test.ts:582:34const = await ; const runtime = ; runtime. =likely benign Test loads the rolldown dev runtime module via import.meta.resolve.Reasoning
Dynamic import of a runtime entry resolved via import.meta.resolve in a rolldown test file; the specifier is a fixed internal package path, not attacker-controlled.
-
const runtimeUrl = import..; const = await ; return ; }likely benign Test helper dynamically imports the rolldown runtime entry.Reasoning
Resolved internal runtime path from import.meta.resolve in a test helper; standard test pattern with no untrusted input.
-
;likely benign Test checks the runtime entry's exports via dynamic import.Reasoning
Same pattern: dynamic import of a fixed runtime module resolved by import.meta.resolve, used to check its export list.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/basic/main.js:2:10likely benign Fixture function with templated dynamic import of local directory module.Reasoning
Fixture for bundler dynamic-import-vars feature; template-literal specifiers are the intended test subject.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/basic/main.js:6:10likely benign Fixture with multi-variable templated dynamic import.Reasoning
Bundler test fixture exercising multi-segment dynamic import patterns; not malicious.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/basic/main.js:10:10likely benign Fixture dynamic import with an inline comment before the template.Reasoning
Bundler fixture with a comment inside import(); tests parser handling of comments, benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/basic/main.js:14:10likely benign Fixture dynamic import with @vite-ignore annotation.Reasoning
Bundler fixture using a vite-ignore annotation with an alias path; benign test case.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/basic/main.js:18:10likely benign Fixture dynamic import with @vite-ignore tag.Reasoning
Bundler fixture for the vite-ignore tag; benign test code.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/filter/main.js:2:10likely benign Fixture with templated dynamic import for filter testing.Reasoning
Fixture for filtering dynamic imports in the bundler test suite; benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/import-with-comment/with-comment-after-paren.js:2:10likely benign Fixture dynamic import with comment after the opening paren.Reasoning
Parser test fixture for comments placed after the paren in import(); benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/import-with-comment/with-comment-before-paren.js:3:10// oxfmt-ignore return import /* comment */ ; }likely benign Fixture dynamic import with comment before the paren.Reasoning
Parser test fixture for comments before the paren in import(); benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:2:10likely benign Fixture templated dynamic import mirroring Vite conventions.Reasoning
Vite-compatibility fixture for dynamic import variables; benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:6:10likely benign Fixture dynamic import using an alias prefix.Reasoning
Vite-compatibility fixture with alias path import; benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:10:10likely benign Dynamic import of a local module path built from a template literal in a test fixture.Reasoning
Test fixture for Vite dynamic import variable handling. The template-literal specifier builds a path from a function argument, but it only resolves local module paths (aliased, relative) inside a test directory. No execution of attacker-controlled data or network fetch is shown.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:14:10likely benign Dynamic import with a query suffix in a test fixture exercising bundler import-variable behavior.Reasoning
Same fixture file. The specifier is a relative path with a query string (?foo=bar), which is a bundler-semantics test case for dynamic import variables, not a payload loader.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:18:10likely benign Dynamic import with a ?raw suffix in a bundler test fixture.Reasoning
Test fixture for the ?raw import suffix handled by bundlers. The import targets a relative local module within the fixture directory.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:22:10likely benign Dynamic import with a ?url suffix in a bundler test fixture.Reasoning
Test fixture for the ?url suffix. The specifier is a relative local path in a test directory, with no sign of remote loading or decoding.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:26:10likely benign Dynamic import whose template includes a nullish-coalescing expression, in a bundler edge-case fixture.Reasoning
Test fixture for wildcard variables in import specifiers. The expression `base ?? foo` is an intentional edge case for the bundler's import-glob analysis, and the target is a local relative module.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:32:10// (`?` cannot be used as a filename on windows) return ; }likely benign Dynamic import with a ?raw suffix in a fixture, with a comment explaining the Windows filename constraint.Reasoning
The comment notes that `?` cannot be used in Windows filenames, which marks this as a deliberate bundler test case. The import is a local relative path inside a fixture.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:38:10// (`?` cannot be used as a filename on windows) return ; }likely benign Dynamic import with a ?worker suffix in a fixture testing unusual path characters.Reasoning
Fixture testing a `?` in a directory name for the ?worker suffix, with a comment about Windows limitations. The import is a relative local path with no payload-loading behavior.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:42:10likely benign Dynamic import of a parent-directory relative module path in a bundler test fixture.Reasoning
Relative parent-directory import in a test fixture, used to check that the bundler resolves dynamic import paths that climb directories. The target is within the repo's test tree.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/dynamic-import-vars/vite/main.js:46:10likely benign Dynamic import of a multi-level parent-directory module path in a bundler test fixture.Reasoning
Multi-level parent-directory relative import in a test fixture for bundler path resolution. It targets another fixture module and performs no network or decode step.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/esm-external-require-plugin/module-exports/_config.ts:17:28asynclikely benign Dynamic import of a local built module in a test config, cast to string to defeat static analysis.Reasoning
Test config in a fixtures directory. The `as string` cast on a literal relative path is a TypeScript idiom that keeps the bundler from statically resolving the import during the test. The target is a local built file.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/builtin-plugin/esm-external-require-plugin/module-exports/_config.ts:18:28const producer = await ; const consumer = await ; .;likely benign Dynamic import of a local dist entry in a test config to verify module exports.Reasoning
Same test config. It imports a local built entry file (./dist/main.js) to check module.exports interop, and the string cast is a test-harness pattern.
-
info
dynamic-executionpackages/rolldown/tests/fixtures/builtin-plugin/import-glob/vite/restore-query-extension/_config.ts:38:53const res = fs.; return `export default `; } }, -
info
dynamic-executionpackages/rolldown/tests/fixtures/builtin-plugin/import-glob/vite/transform/_config.ts:35:53const res = fs.; return `export default `; } }, -
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/misc/rolldown-file-url/_config.ts:36:23afterTest:likely benign Dynamic import of a local built entry in a rolldown file-URL test to validate asset paths.Reasoning
Test afterTest hook in a fixture. It imports a local built output (./dist/entries/main.mjs) and checks the resolved file URL path. The string cast is a test-harness idiom.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/misc/rollup-file-url-chunk/_config.ts:30:24afterTest:likely benign Dynamic import of a local built chunk and a derived file URL in a rollup test fixture.Reasoning
Test hook imports a local built main.js, then builds a URL from its default export and imports it. This is a test of chunked file URL resolution. The target is a local build artifact within the fixture.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/misc/rollup-file-url-chunk/_config.ts:32:23const depUrl = .; const dep = await ; .; },likely benign Test fixture that dynamically imports a chunk by computed file URL.Reasoning
The dynamic import specifier is built from a URL resolved relative to import.meta.url, inside a test fixture that checks Rollup's file-URL chunk handling. The pattern is normal for bundler tests and nothing in the snippet is hidden or malicious.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/misc/rollup-file-url/_config.ts:38:23afterTest:likely benign Dynamic import of a local built entry in a rollup file-URL test to validate asset paths.Reasoning
Same pattern as the rolldown fixture: a test hook imports a local dist entry and checks the file URL resolution. Nothing suggests remote fetch or hidden execution.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/output/es-module/common-chunks/_config.ts:24:27) ., ).; },likely benign Test assertion that requires each emitted chunk by template path.Reasoning
A template-literal require over the build output directory inside a test assertion that checks emitted chunk module shape. This is a routine test harness pattern.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/output/es-module/false/_config.ts:24:28) ., ).; },likely benign Test assertion that requires emitted chunks to check the __esModule flag.Reasoning
Same test-harness pattern as the sibling fixtures: requiring generated chunks from ./dist to check the __esModule flag. No obfuscation or malicious behavior is visible.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/output/es-module/if-default-prop-false/_config.ts:26:28) ., ).; },likely benign Test assertion that requires a generated bundle and checks a nested export property.Reasoning
Test fixture that requires generated bundles from the dist directory and checks a nested property. Benign test scaffolding.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/output/es-module/if-default-prop-true/_config.ts:26:27) ., ).; },likely benign Test assertion that requires a generated bundle and checks a nested export property.Reasoning
Same test scaffolding pattern as the other es-module fixtures, requiring build output in a test assertion. Nothing suspicious.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/output/es-module/true/_config.ts:24:27) ., ).; },likely benign Test assertion that requires emitted chunks to verify ES module output.Reasoning
Routine test harness requiring generated chunks from the dist folder to verify module output. Benign.
-
info
warn→ info by reviewdynamic-importpackages/rolldown/tests/fixtures/output/minify/dce-only/main.js:3:1;likely benign Minifier fixture with a dynamic import of the node:module built-in.Reasoning
The import specifier is the literal 'node:module' with a vite-ignore comment. The AST pass flagged it only because of the comment placement, and it is a static built-in import.
-
info
warn→ info by reviewencoding-base64packages/rolldown/tests/fixtures/output/sourcemap/methods/_config.ts:18:52.;likely benign Inline base64 source map data URL inside a sourcemap test snapshot.Reasoning
The base64 is a standard inline source map data URL in an inline snapshot assertion. It decodes to ordinary sourcemap JSON, so this is expected test output, not a payload.
-
info
warn→ info by reviewencoding-base64packages/rolldown/tests/fixtures/output/sourcemap/methods/_config.ts:26:52.; },likely benign Inline base64 source map data URL in a second sourcemap test snapshot.Reasoning
Another inline sourcemap data URL expected in a snapshot assertion. It is a normal artifact of testing source map generation.
-
info
warn→ info by reviewencoding-base64packages/rolldown/tests/magic-string/MagicString.test.ts:233:53map., 'data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoib3V0cHV0Lm1kIiwic291cmNlcyI6WyJpbnB1dC5tZCJdLCJzb3VyY2VzQ29udGVudCI6WyJhYmNkZWZnaGlqa2wiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IkFBQUEsQ0FBQyxDQUFDLENBQU8sQ0FBQyxDQUFDIn0=', );likely benign Base64 sourcemap data URL used as an expected value in a MagicString test.Reasoning
The blob is a base64 source map data URL passed as an expected value to a MagicString test. It is standard test data with no execution path.
-
info
warn→ info by reviewencoding-base64packages/rolldown/tests/magic-string/MagicString.test.ts:319:53map., 'data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoib3V0cHV0Lm1kIiwic291cmNlcyI6WyJpbnB1dC5tZCJdLCJzb3VyY2VzQ29udGVudCI6WyJhYmNkZWZnaGlqa2wiXSwibmFtZXMiOltdLCJtYXBwaW5ncyI6IkFBQUEsR0FBRyxHQUFNLENBQUMifQ==', );likely benign Base64 sourcemap data URL expected value in a MagicString test.Reasoning
Same as the other MagicString test: a base64-encoded source map literal compared against generated output. Benign test data.
-
// matching JS behavior: 'a🤷b'.slice(2) === '\uDD37b' assert.; // slice(0, 2) ends at low surrogate — returns 'a' + lone high surrogate // matching JS behavior: 'a🤷b'.slice(0, 2) === 'a\uD83E' -
// matching JS behavior: 'a🤷b'.slice(0, 2) === 'a\uD83E' assert.; // slice(3) is 'b' assert.; -
assert.; assert.; }); }); -
} return ; }likely benign Test helper that loads a built native binding by computed file name.Reasoning
A small test helper that requires a native binding from the dist directory by a computed filename. The path is local and built by the project, so this is a plausible loader, though the dynamic path is worth a glance.
-
-
info
warn→ info by reviewlong-linepackages/rolldown/tests/stability/issue-3453/src/lib/file1.js:11670:1/^likely benign Long regex listing HTML and React attribute names in a vendored library file.Reasoning
A very long regex alternation of React DOM attribute names inside a vendored library file. Long lines are typical of minified or generated library code, and the content is a plain attribute whitelist.
-
// System fonts - Taken from https://furbo.org/stuff/systemfonts-new.html - "All Platforms" section 'system-ui|-apple-system|BlinkMacSystemFont|Segoe UI|Roboto|Oxygen|Ubuntu|Cantarell|Fira Sans|Droid Sans|Helvetica Neue|sans-serif' ); const fontFamily = -
children: 'Jared Spool, Co-Founder of UIE asks, “What was the most important thing you learned yesterday, and how will it impact what you do in the future?”', }), /*#__PURE__*/ -
children: "People don't always know what they want, even if they think the do. As Joe Leech, a UX psychologist says, \"People want more choices, but can't deal with them.”", }), /*#__PURE__*/ -
children: 'Jared Spool, Wsp\xf3łzałożyciel UIE pyta: „Co było najważniejszą rzeczą, jaką wczoraj się nauczyłeś, i w jaki spos\xf3b to wpłynie na to, co robisz w przyszłości?”', }), /*#__PURE__*/ -
info
warn→ info by reviewlong-linepackages/rolldown/tests/stability/issue-3453/src/lib/file37.js:37:1/^likely benign A very long regex literal containing an alphabetical list of React/HTML attribute names, inside a test fixture file.Reasoning
The raw pass flagged a long line only by length (3972 characters). The visible snippet is a regular expression built from a long alternation of React DOM attribute names (children, dangerouslySetInnerHTML, autoFocus, etc.), which is a typical generated or prop-whitelist pattern. It is in a test fixture for a stability issue, and nothing in the snippet suggests encoding, execution, or concealment. The long-line signal is a known high-false-positive raw heuristic.
-
'UNKNOWN-SESSION', 'unKnown-session', 'unknown-ſession', 'unknown-seßion',
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.
&&