ripgrep recursively searches directories for a regex pattern while respecting your gitignore
This report summarizes scanner evidence for BurntSushi/ripgrep, a Rust project with 69,012 GitHub stars. SynthScan examined 66,016 lines of code across 159 source files, recording 353 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 5.8 (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? 348 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 5 finding(s).
Which changes need focused human review? 353 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 353 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 | crates/searcher/src/line_buffer.rs | 1 | use std::io; | COMMENT |
| LOW | crates/searcher/src/line_buffer.rs | 41 | COMMENT | |
| LOW | crates/searcher/src/line_buffer.rs | 141 | pub(crate) fn capacity( | COMMENT |
| LOW | crates/searcher/src/line_buffer.rs | 161 | &mut self, | COMMENT |
| LOW | crates/searcher/src/line_buffer.rs | 241 | } | COMMENT |
| LOW | crates/searcher/src/line_buffer.rs | 281 | /// This is a convenience function for `consume(buffer.len())`. | COMMENT |
| LOW | crates/searcher/src/line_buffer.rs | 301 | pos: usize, | COMMENT |
| LOW | crates/searcher/src/line_buffer.rs | 381 | /// | COMMENT |
| LOW | crates/searcher/src/sink.rs | 61 | COMMENT | |
| LOW | crates/searcher/src/sink.rs | 81 | /// this, which already implements `SinkError`. | COMMENT |
| LOW | crates/searcher/src/sink.rs | 101 | /// [`sinks`] module. | COMMENT |
| LOW | crates/searcher/src/sink.rs | 121 | /// If this returns an error, then searching is stopped immediately, | COMMENT |
| LOW | crates/searcher/src/sink.rs | 141 | /// of the searcher. | COMMENT |
| LOW | crates/searcher/src/sink.rs | 161 | /// `false`, then searching is stopped immediately and `finish` is called. | COMMENT |
| LOW | crates/searcher/src/sink.rs | 181 | /// | COMMENT |
| LOW | crates/searcher/src/sink.rs | 201 | /// | COMMENT |
| LOW | crates/searcher/src/sink.rs | 381 | } | COMMENT |
| LOW | crates/searcher/src/sink.rs | 461 | &self.kind | COMMENT |
| LOW | crates/searcher/src/sink.rs | 481 | self.absolute_byte_offset | COMMENT |
| LOW | crates/searcher/src/sink.rs | 501 | /// `Sink`. | COMMENT |
| LOW | crates/searcher/src/sink.rs | 521 | COMMENT | |
| LOW | crates/searcher/src/sink.rs | 561 | None => { | COMMENT |
| LOW | crates/searcher/src/sink.rs | 621 | } | COMMENT |
| LOW | crates/searcher/src/lines.rs | 41 | /// This iterator avoids borrowing the bytes themselves, and instead requires | COMMENT |
| LOW | crates/searcher/src/lines.rs | 61 | /// | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 41 | /// true, which is why binary detection is disabled by default. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 61 | /// This is the default. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 81 | } | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 121 | /// | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 161 | passthru: bool, | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 241 | /// to construct a `Searcher` from a `SearcherBuilder`. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 361 | } | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 381 | /// will be used if possible and if they are enabled, which avoids using | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 421 | /// Whether to enable the "passthru" feature or not. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 441 | /// * When searching using a fixed size buffer, the heap limit controls | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 461 | self.config.heap_limit = bytes; | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 481 | /// the memory maps. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 521 | /// transcoded using the encoding, unless a BOM is present. If a BOM is | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 541 | /// Enable automatic transcoding based on BOM sniffing. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 561 | /// This is useful for searching sorted files where it is expected that all | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 581 | /// By default, no limit is set. | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 601 | /// public API methods, which can be queried in implementations of `Sink` | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 621 | /// multi line search. In particular, multi line searches cannot be | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 861 | /// Returns true if and only if this searcher is configured to perform | COMMENT |
| LOW | crates/searcher/src/searcher/mod.rs | 881 | /// | COMMENT |
| LOW | crates/searcher/src/searcher/mmap.rs | 21 | impl Default for MmapChoice { | COMMENT |
| LOW | crates/searcher/src/searcher/mmap.rs | 41 | /// without simultaneously negating some or all of their benefits. | COMMENT |
| LOW | crates/searcher/src/searcher/glue.rs | 221 | let line = | COMMENT |
| LOW | crates/core/haystack.rs | 121 | /// Returns true if and only if this entry corresponds to a haystack to | COMMENT |
| LOW | crates/core/main.rs | 21 | // use the system allocator. On Linux, this would normally be glibc's | COMMENT |
| LOW | crates/core/main.rs | 421 | err_message!( | COMMENT |
| LOW | crates/core/messages.rs | 21 | static MESSAGES: AtomicBool = AtomicBool::new(false); | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 221 | // particular, we generally want to show line numbers by | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 341 | /// stdout. | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 681 | /// Generally speaking, quiet mode means that ripgrep should not print | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 761 | /// Given an iterator of haystacks, sort them if necessary. | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 861 | /// the available number of cores) and whether ripgrep's mode supports | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 961 | /// conversions as a way to communicate changes to other conversions. For | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 1001 | /// The number of patterns can be empty, e.g., via `-f /dev/null`. | COMMENT |
| LOW | crates/core/flags/hiargs.rs | 1081 | } | COMMENT |
| 280 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | crates/core/flags/complete/rg.zsh | 658 | # ------------------------------------------------------------------------------ | COMMENT |
| MEDIUM⚡ | crates/core/flags/complete/rg.zsh | 683 | # ------------------------------------------------------------------------------ | COMMENT |
| MEDIUM⚡ | crates/core/flags/complete/rg.zsh | 685 | # ----------- | COMMENT |
| MEDIUM⚡ | crates/core/flags/complete/rg.zsh | 689 | # ------------------------------------------------------------------------------ | COMMENT |
| MEDIUM⚡ | crates/core/flags/complete/rg.zsh | 696 | # ------------------------------------------------------------------------------ | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | crates/core/flags/complete/rg.zsh | 567 | # The next line defines `--color`. In this example, `--color` doesn't have a | COMMENT |
| HIGH | crates/core/flags/complete/rg.zsh | 578 | # The last line defines an operand (a non-option argument). In this example, the | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | crates/core/flags/lowargs.rs | 246 | /// Automatically determine the binary mode to use. Essentially, when | COMMENT |
| MEDIUM | crates/core/flags/complete/rg.zsh | 512 | # comprehensive; it covers just enough of the basic structure, syntax, and | COMMENT |
| MEDIUM | crates/cli/src/decompress.rs | 287 | /// The purpose of this reader is to provide a seamless way to decompress the | COMMENT |
| MEDIUM | tests/util.rs | 522 | /// how to disable it. Absolutely fucking bonkers. | COMMENT |
| LOW | .github/workflows/ci.yml | 39 | # different OS will just use normal cargo. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | crates/ignore/src/gitignore.rs | 217 | /// NOTE: This method is more expensive than walking the directory hierarchy | COMMENT |