Utilities
Search source files with ripgrep
ripgrep-search is a source-search node that returns native ripgrep regex events and offsets as JSONL.
overview
What ripgrep-search does
Search a copied folder with a case-sensitive Rust regular expression. Native JSONL events identify matching paths, line content and byte offsets, followed by summary statistics. Hidden text is included; repository ignore and config files are not loaded. Generated .git, node_modules, .venv and target folders are excluded.
Native Rust regex JSONL, hidden text included, config/ignore files disabled; 1000 files, 1 MiB/file, 20 MiB, 100 matching lines/file, 60 seconds
No matches is a valid native summary. Invalid regexes and runtime/input failures fail the operation; the source remains unchanged.
This operation uses 15.2.0. Upstream license: MIT. The source link identifies the program used by this node.
use cases
Where ripgrep-search fits
Locate a recurring identifier
Find every matching line with a case-sensitive Rust regex.
Collect source locations
Use native paths and byte offsets to point a later review at the matching text.
Handle no matches explicitly
Treat a zero-match summary as a result instead of a task failure.
reference
ripgrep-search inputs and flags
| Name | Type | Flag | Description |
|---|---|---|---|
| source | FOLDER | --source | Folder, at most 1000 files, 1 MiB per file and 20 MiB total. Symlinks refused. Generated .git/node_modules/.venv/target folders excluded; hidden text included; binary files use native handling. |
| pattern | STRING | --pattern | Rust regex, 1-4096 UTF-8 bytes. Case sensitive. At most 100 matching lines per file; 60 seconds and 16 MiB output. No matches is a valid native summary. |
Showing key inputs. ripgrep-search exposes 2 inputs in total.
example
Run ripgrep-search
python3 /app/run.py --source ./source --pattern 'needle' ./output{
"type": "summary",
"data": {
"stats": {
"matched_lines": 4,
"matches": 5
}
}
}guidance
Choosing ripgrep-search
Use ripgrep-search when later steps need structured regex matches and offsets. Fixed-string filters are simpler for literal line selection; this operation does not parse source syntax.
fgrep-by-string
Selects literal matching lines rather than native regex JSONL events.
faq
ripgrep-search questions
related
More Utilities tools
browser-fetch
Headless Chromium render: requested URL, final URL, status, and title next to the page.
cewl
Spider a URL and return a wordlist for password crackers.
csvkit
SQL on one CSV. The table name is the file stem.
dnsgen
Wordlist and mined-word subdomain permutation.
duckdb
In-process SQL on CSV, JSON, and Parquet. No server.
edge-tts
Microsoft Edge neural speech from text or a script file. No API key.
Run ripgrep-search yourself
The synthetic run checks jsonl search events. The excerpt shows selected native fields asserted by saved passing platform verifier; reconstructed excerpt, not full raw artifact. The command shown is the container entrypoint with example paths, not a host-installed CLI command.
Facts on this page come from the live Trickest tool library.