Additional completion definitions for Zsh.
This report summarizes scanner evidence for zsh-users/zsh-completions, a Shell project with 7,897 GitHub stars. SynthScan examined 865 lines of code across 5 source files, recording 9 pattern matches distributed across 3 syntactic categories. The legacy adjusted pattern signal is 38.2 (High 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? 2 finding(s).
Are imports declared and package/API names verified? 2 finding(s).
Are wrappers, guards, and repeated structures necessary? 5 finding(s).
Which changes need focused human review? 9 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 9 distinct pattern matches across 3 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 |
|---|---|---|---|---|
| MEDIUM | src/_setup.py | 2 | # ------------------------------------------------------------------------------ | COMMENT |
| MEDIUM⚡ | src/_setup.py | 22 | # ------------------------------------------------------------------------------ | COMMENT |
| MEDIUM⚡ | src/_setup.py | 24 | # ----------- | COMMENT |
| MEDIUM⚡ | src/_setup.py | 28 | # ------------------------------------------------------------------------------ | COMMENT |
| MEDIUM⚡ | src/_setup.py | 34 | # ------------------------------------------------------------------------------ | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | src/_setup.py | 114 | _describe -t commands 'setup.py subcommand' _setuppy_cmds || compadd "$@" - ${(s.:.)${(j.:.)_setuppy_syns}} | CODE |
| HIGH | src/_setup.py | 121 | _call_function ret _setuppy_$cmd || _message 'no more arguments' | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | src/_setup.py | 1 | #compdef setup.py | COMMENT |
| LOW | src/_setup.py | 21 | # THE SOFTWARE. | COMMENT |