Pretty, minimal and fast ZSH prompt
This report summarizes scanner evidence for sindresorhus/pure, a Shell project with 14,441 GitHub stars. SynthScan examined 6,658 lines of code across 30 source files, recording 33 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 6.6 (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? 32 finding(s).
Are imports declared and package/API names verified? 1 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 33 finding(s).
Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.
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 33 distinct pattern matches across 4 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 | pure.plugin.zsh | 265 | # Check if we should display the virtual env (psvar[20]). | COMMENT |
| LOW | pure.plugin.zsh | 268 | # Check if a Conda environment is active and display its name. | COMMENT |
| LOW | pure.plugin.zsh | 451 | # Set remote to only fetch information for the current branch. Use the upstream's ref on the remote, as it can have a | COMMENT |
| LOW | pure.plugin.zsh | 571 | # Check if Node.js version display is enabled (independent of Git). | COMMENT |
| LOW | pure.plugin.zsh | 595 | # Check if git integration is enabled (default: yes). | COMMENT |
| LOW | pure.plugin.zsh | 713 | # Check if the working tree is dirty. | COMMENT |
| LOW | pure.plugin.zsh | 809 | # Check if Git top-level has changed. | COMMENT |
| LOW | pure.plugin.zsh | 996 | # Check if hostname display is enabled (default: yes). | COMMENT |
| LOW | pure.zsh | 265 | # Check if we should display the virtual env (psvar[20]). | COMMENT |
| LOW | pure.zsh | 268 | # Check if a Conda environment is active and display its name. | COMMENT |
| LOW | pure.zsh | 451 | # Set remote to only fetch information for the current branch. Use the upstream's ref on the remote, as it can have a | COMMENT |
| LOW | pure.zsh | 571 | # Check if Node.js version display is enabled (independent of Git). | COMMENT |
| LOW | pure.zsh | 595 | # Check if git integration is enabled (default: yes). | COMMENT |
| LOW | pure.zsh | 713 | # Check if the working tree is dirty. | COMMENT |
| LOW | pure.zsh | 809 | # Check if Git top-level has changed. | COMMENT |
| LOW | pure.zsh | 996 | # Check if hostname display is enabled (default: yes). | COMMENT |
| LOW | async.zsh | 227 | # Check if a worker should perform unique jobs, unless | COMMENT |
| LOW | async.zsh | 230 | # Check if a previous job is still running, if yes, | COMMENT |
| LOW | async.zsh | 559 | # Check if the worker exists | COMMENT |
| LOW | async.zsh | 711 | # Check if zsh/zpty returns a file descriptor or not, | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | pure.plugin.zsh | 1 | # Pure | COMMENT |
| LOW | pure.plugin.zsh | 1181 | if (( $+functions[add-zle-hook-widget] )); then | COMMENT |
| LOW | pure.plugin.zsh | 1201 | # psvar[16] = git action (e.g. rebase, merge) | COMMENT |
| LOW | pure.plugin.zsh | 1261 | # Combine the parts with conditional logic. First the `:+` operator is | COMMENT |
| LOW | pure.zsh | 1 | # Pure | COMMENT |
| LOW | pure.zsh | 1181 | if (( $+functions[add-zle-hook-widget] )); then | COMMENT |
| LOW | pure.zsh | 1201 | # psvar[16] = git action (e.g. rebase, merge) | COMMENT |
| LOW | pure.zsh | 1261 | # Combine the parts with conditional logic. First the `:+` operator is | COMMENT |
| LOW | async.zsh | 81 | COMMENT | |
| LOW | async.zsh | 281 | # usage: | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | pure.plugin.zsh | 871 | # No remote available, make sure to clear git arrows if set. | COMMENT |
| LOW | pure.zsh | 871 | # No remote available, make sure to clear git arrows if set. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | tests/git-dirty.zsh | 21 | command git config user.email "test@test.com" | CODE |