paul's fish, bash, git, etc config files. good stuff.
This report summarizes scanner evidence for paulirish/dotfiles, a Shell project with 4,360 GitHub stars. SynthScan examined 12,139 lines of code across 64 source files, recording 43 pattern matches distributed across 11 syntactic categories. The legacy adjusted pattern signal is 5.7 (Moderate 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.
Can maintainers explain intent, assumptions, and trade-offs? 41 finding(s).
Are imports declared and package/API names verified? 1 finding(s).
Are wrappers, guards, and repeated structures necessary? 2 finding(s).
Which changes need focused human review? 43 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 43 distinct pattern matches across 11 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 | .git-completion.bash | 1 | # bash/zsh completion support for core Git. | COMMENT |
| LOW | .git-completion.bash | 21 | # *) file paths within current working directory and index | COMMENT |
| LOW | .git-completion.bash | 41 | # scripts, define a function of the form '_git_${subcommand}' while replacing | COMMENT |
| LOW | .git-completion.bash | 61 | # _git_log and __gitk_main. | COMMENT |
| LOW | .git-completion.bash | 81 | # When set to "1" suggest all options, including options which are | COMMENT |
| LOW | .git-completion.bash | 261 | # | COMMENT |
| LOW | .git-completion.bash | 281 | # This function can be used to access a tokenized list of words | COMMENT |
| LOW | .git-completion.bash | 381 | COMMENT | |
| LOW | .git-completion.bash | 481 | unset ${(M)${(k)parameters[@]}:#__gitcomp_builtin_*} 2>/dev/null | COMMENT |
| LOW | .git-completion.bash | 581 | compopt -o filenames +o nospace 2>/dev/null || | COMMENT |
| LOW | .git-completion.bash | 961 | COMMENT | |
| LOW | .git-completion.bash | 3321 | _found=1 | COMMENT |
| LOW | .git-completion.bash | 3341 | # on paths that exist in the current working tree, | COMMENT |
| LOW | .git-completion.bash | 3381 | # Since sparse-index is limited to cone-mode, in non-cone-mode the | COMMENT |
| LOW | .git-completion.bash | 3401 | # completion will actually complete an entry and let us move on to | COMMENT |
| LOW | .git-completion.bash | 3421 | # the user wants all '.config' files throughout the | COMMENT |
| LOW | setup-a-new-machine.sh | 61 | COMMENT | |
| LOW | setup-a-new-machine.sh | 221 | COMMENT | |
| LOW | setup-chromium.sh | 1 | COMMENT | |
| LOW | .eslintrc.js | 1 | module.exports = { | COMMENT |
| LOW | bin/render-streaming-markdown.ts | 41 | // // Flush everything up to it | COMMENT |
| LOW | bin/start-devtools-servers.sh | 21 | # ~/Library/Workflows/Applications/MyLoginStuff-streamdeck-displayswap-etc.automator.app | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | symlink-setup.sh | 111 | # Print output in red | COMMENT |
| LOW⚡ | symlink-setup.sh | 116 | # Print output in purple | COMMENT |
| LOW⚡ | symlink-setup.sh | 121 | # Print output in yellow | COMMENT |
| LOW | symlink-setup.sh | 135 | # Print output in green | COMMENT |
| LOW | bin/diagnose-cloudtop.sh | 52 | # Check if cssom repo has fsmonitor enabled | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | .git-completion.bash | 254 | # The following function is based on code from: | COMMENT |
| MEDIUM | .git-completion.bash | 486 | # This function is equivalent to | COMMENT |
| MEDIUM | .git-completion.bash | 528 | # This function is equivalent to | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | .git-completion.bash | 1704 | # logic, as requested by the user. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | agents/skills/distill-page/updating.md | 9 | ## Step 1: Run the Update Script | COMMENT |
| LOW | agents/skills/distill-page/updating.md | 21 | ## Step 2: Investigate Changes in the Proto | COMMENT |
| LOW | agents/skills/distill-page/updating.md | 44 | ## Step 3: Run the Test Suite | COMMENT |
| LOW | agents/skills/distill-page/updating.md | 57 | ## Step 4: Implement Improvements (If applicable) | COMMENT |
| LOW | agents/skills/distill-page/updating.md | 66 | ## Step 5: Amend the Commit | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | chromium.sh | 51 | # you can also add any extra args: `cr --user-data-dir=/tmp/lol123" | COMMENT |
| MEDIUM | .git-completion.bash | 32 | # If you use complex aliases of form '!f() { ... }; f', you can use the null | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | agents/skills/qmd-expert/SKILL.md | 90 | # using the -l flag (e.g. -l 20) to keep the context window lean. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | bin/fish_profile_to_flamegraph.py | 60 | print(f"Error: Profiling output file not found at {profiling_filepath}") | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | bin/fish_profile_to_flamegraph.py | 4 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | bin/fish_profile_to_flamegraph.py | 19 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …ents/skills/distill-page/scripts/decode_annotations.ts | 959 | export function decodeAnnotatedPageContent(base64String: string): AnnotatedPageContent { | CODE |