Routing and navigation for React Native and Web apps
This report summarizes scanner evidence for react-navigation/react-navigation, a TypeScript project with 24,517 GitHub stars. SynthScan examined 195,510 lines of code across 667 source files, recording 69 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.4 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 29 finding(s).
Are imports declared and package/API names verified? 40 finding(s).
Are wrappers, guards, and repeated structures necessary? 21 finding(s).
Which changes need focused human review? 69 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 69 distinct pattern matches across 5 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | example/e2e/maestro/tab-view-scrollable-tab-bar.yml | 15 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/stack-header-customization.yml | 20 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/stack-prevent-remove.yml | 12 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/stack-prevent-remove.yml | 51 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/tab-view-custom-tab-bar.yml | 21 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/tab-view-custom-tab-bar.yml | 48 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/drawer-master-detail.yml | 26 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/navigator-layout.yml | 24 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | …mple/e2e/maestro/native-stack-header-customization.yml | 9 | TEXT: 'What is Lorem Ipsum?' | CODE |
| LOW | …mple/e2e/maestro/native-stack-header-customization.yml | 21 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | …mple/e2e/maestro/native-stack-header-customization.yml | 29 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/tab-view-auto-width-tab-bar.yml | 13 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | …mple/e2e/maestro/native-bottom-tabs-custom-tab-bar.yml | 8 | TEXT: 'What is Lorem Ipsum?' | CODE |
| LOW | …mple/e2e/maestro/native-bottom-tabs-custom-tab-bar.yml | 14 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | …mple/e2e/maestro/native-bottom-tabs-custom-tab-bar.yml | 32 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/native-stack-prevent-remove.yml | 12 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/native-stack-prevent-remove.yml | 51 | text: 'What is Lorem Ipsum?' | CODE |
| LOW | example/e2e/maestro/tab-view-scroll-adapter.yml | 13 | text: 'What is Lorem Ipsum?' | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 76 | <Heading>What is Lorem Ipsum?</Heading> | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 78 | Lorem Ipsum is simply dummy text of the printing and typesetting | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 79 | industry. Lorem Ipsum has been the industry's standard dummy text | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 84 | of Letraset sheets containing Lorem Ipsum passages, and more recently | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 86 | of Lorem Ipsum. | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 95 | Contrary to popular belief, Lorem Ipsum is not simply random text. It | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 99 | Latin words, consectetur, from a Lorem Ipsum passage, and going through | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 101 | undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 105 | Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 105 | Ipsum, "Lorem ipsum dolor sit amet..", comes from a line in | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 109 | The standard chunk of Lorem Ipsum used since the 1500s is reproduced | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 119 | using Lorem Ipsum is that it has a more-or-less normal distribution of | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 122 | and web page editors now use Lorem Ipsum as their default model text, | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 123 | and a search for "lorem ipsum" will uncover many web sites | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 130 | There are many variations of passages of Lorem Ipsum available, but the | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 133 | are going to use a passage of Lorem Ipsum, you need to be sure there | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 135 | Lorem Ipsum generators on the Internet tend to repeat predefined chunks | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 138 | model sentence structures, to generate Lorem Ipsum which looks | CODE |
| LOW⚡ | example/src/Shared/Article.tsx | 139 | reasonable. The generated Lorem Ipsum is therefore always free from | CODE |
| LOW | example/src/Screens/NativeStackFormSheet.tsx | 140 | 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam ' + | CODE |
| LOW | example/src/Screens/NativeStackFormSheet.tsx | 140 | 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nullam ' + | CODE |
| LOW | packages/core/src/__tests__/queryString.test.tsx | 27 | { query: 'first+name=Jane+Doe', expected: { 'first name': 'Jane Doe' } }, | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | example/__typechecks__/static.check.tsx | 416 | function StaticNavigatorHookTypeChecks() { | CODE |
| LOW | example/src/Screens/ComponentsMaterialSymbols.tsx | 69 | export function ComponentsMaterialSymbols(_: StaticScreenProps<{}>) { | CODE |
| LOW | scripts/measure-typescript.ts | 382 | const dynamicConsumers = `function UseDynamicParamListToParamList() { | CODE |
| LOW | scripts/measure-typescript.ts | 403 | function UseDynamicParamListToNavigator() { | CODE |
| LOW | scripts/measure-typescript.ts | 424 | function UseDynamicNavigatorToParamList() { | CODE |
| LOW | scripts/measure-typescript.ts | 443 | function UseStaticParentToStaticChild() { | CODE |
| LOW | packages/core/src/NavigationIndependentTree.tsx | 30 | export function NavigationIndependentTree({ | CODE |
| LOW | packages/core/src/getStateFromPath.tsx | 518 | function getSortedNormalizedConfigs( | CODE |
| LOW | packages/core/src/getStateFromPath.tsx | 606 | function checkForDuplicatedConfigs( | CODE |
| LOW | packages/core/src/useNavigationIndependentTree.tsx | 5 | export function useNavigationIndependentTree() { | CODE |
| LOW | …ckages/core/src/useFocusedListenersChildrenAdapter.tsx | 19 | export function useFocusedListenersChildrenAdapter({ | CODE |
| LOW | packages/core/src/useNavigationState.tsx | 187 | export function NavigationStateListenerProvider({ | CODE |
| LOW | packages/core/src/useNavigationState.tsx | 252 | export function NamedNavigationStateListenerProvider({ | CODE |
| LOW | packages/core/src/getFocusedRouteNameFromRoute.tsx | 5 | export function getFocusedRouteNameFromRoute( | CODE |
| LOW | packages/core/src/NavigationBuilderContext.tsx | 92 | export function useNavigationBuilderContext() { | CODE |
| LOW | …kages/native/src/createStandardNavigationFactories.tsx | 98 | function StandardNavigationNavigator(props: any) { | CODE |
| LOW | packages/devtools/src/parseHermesStack.tsx | 71 | function isInternalBytecodeSourceUrl(sourceUrl: string): boolean { | CODE |
| LOW | packages/devtools/src/useReduxDevToolsExtension.tsx | 21 | export function useReduxDevToolsExtension( | CODE |
| LOW | …ative-stack/src/utils/useInvalidPreventRemoveError.tsx | 6 | export function useInvalidPreventRemoveError( | CODE |
| LOW | …stack/src/TransitionConfigs/CardStyleInterpolators.tsx | 308 | export function forRevealFromBottomAndroid({ | CODE |
| LOW | …stack/src/TransitionConfigs/CardStyleInterpolators.tsx | 407 | export function forScaleFromCenterAndroid({ | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | packages/core/src/useNavigationBuilder.tsx | 841 | setKey(navigatorKey); | COMMENT |
| LOW | packages/core/src/useNavigationState.tsx | 101 | entry: NavigationStateEntry | null; | COMMENT |
| LOW | packages/core/src/getActionFromState.tsx | 101 | pop?: boolean | undefined; | COMMENT |
| LOW | packages/native/ios/ReactNavigationCornerInsetView.mm | 1 | #import "ReactNavigationCornerInsetView.h" | COMMENT |
| LOW | packages/native/src/createMemoryHistory.tsx | 161 | return new Promise<void>((resolve, reject) => { | COMMENT |
| LOW | …react-native-drawer-layout/src/views/Drawer.native.tsx | 481 | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | packages/bottom-tabs/src/views/BottomTabBar.tsx | 410 | // Absolutely position the tab bar so that the content is below it | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | packages/core/src/useOnPreventRemove.tsx | 63 | // First, we need to check if any child screens want to prevent it | COMMENT |