ripgrep, run as rg, is a free command-line tool that searches every file in a folder and its subfolders for a word or pattern and prints each match with its file name and line number. Type rg TODO in a project and you see every TODO in a fraction of a second, with the files your .gitignore lists, hidden files and binary files skipped for you.
It earns its place because it is one of the fastest search tools there is and it does the sensible thing by default, which plain grep does not. It understands regular expressions, can limit a search to file types (rg -t py), searches compressed files on request, and is the search engine inside VS Code's find-in-files. If you have ever waited on grep -r, this is the upgrade.
ripgrep is written in Rust by Andrew Gallant (BurntSushi), who started it in 2016, and is dual-licensed under MIT or the Unlicense. It has about 70,000 stars and around 480 contributors. Version 15.2.0 came out on 15 July 2026.
- Repository: github.com/BurntSushi/ripgrep
- Licence: Unlicense (The Unlicense)
- Language: Rust. Stars: 70K. Forks: 3,516. Last push: Nov 9, 2026.
- Scan: safe, Nov 16, 2026, commit 178cc02
Who it is for
Developers, writers with folders of notes, sysadmins digging through logs and anyone who needs to find text across many files quickly. It works on macOS, Linux and Windows from a terminal.
Getting started
1. Install on macOS or Linux with Homebrew
brew install ripgrep2. Or on Windows, with winget
winget install BurntSushi.ripgrep.MSVC3. Or on Ubuntu and Debian
sudo apt install ripgrep4. Search the current folder and everything below it
rg "search words"5. Only search one file type, here Python files
rg -t py "def main"Package managers install a single rg program and change nothing else. To also search files your .gitignore hides, add -uuu. Our scan covers the source code, not the prebuilt binaries from GitHub releases or package managers.
Safety scan
We cloned BurntSushi/ripgrep at commit 178cc02 on Nov 16, 2026 and ran the checks described on the GitHub Tools page: credential patterns, decode-and-execute code, install-time scripts, committed binaries, risky CI workflows, every host the code talks to, known vulnerabilities in pinned dependencies, and project hygiene. A person read every hit. This is what we found.
- 0 secret hits and no committed binaries across 225 files and about 63,000 lines, almost all of it Rust.
- 0 pattern hits. ripgrep runs other programs only when you ask: --search-zip calls tools like gzip or xz to read compressed files, and --pre runs a preprocessor command you name. build.rs only records the git revision and embeds a Windows manifest for long file paths.
- No install script. Releases are single prebuilt binaries, and the usual route is a package manager such as Homebrew, winget, Chocolatey, Scoop or apt.
- 0 advisories across the 60 Rust packages in Cargo.lock and the 21 in the fuzzing setup.
- The hosts in the code are documentation links, crates.io and GitHub; the program itself contacts no server. Two workflows, CI and release, with no pull_request_target, but none of the 9 third-party actions is pinned to a commit. No security policy file, Dependabot or CodeQL. OpenSSF Scorecard gives it 5.0 out of 10.
What the scanner counted
| Check | Result |
|---|---|
| Secrets | None found. |
| Suspicious code | None found. |
| Install-time code | 1 Cargo build script |
| Committed binaries | None. |
| CI workflows | 2 workflows. None use pull_request_target. 9 of 9 third-party actions pinned to a tag rather than a commit. |
| Network hosts | 18 distinct hosts referenced from source; most often github.com, docs.rs, doc.rust-lang.org, crates.io. No URLs to bare IP addresses. |
| Known vulnerabilities | 0 advisories across 81 pinned packages: 0 critical, 0 high, 0 moderate, 0 low. Cargo.lock: 60 packages, 0 advisories; fuzz/Cargo.lock: 21 packages, 0 advisories. |
| Project hygiene | Has licence file, contributing guide. Missing security policy, automated dependency updates, CodeQL. |
| OpenSSF Scorecard | 5.0 out of 10, as of Nov 16, 2026. |
By the numbers
| Stars | 70K |
|---|---|
| Forks | 3,516 |
| Contributors | 485 |
| Commits | 2,304 |
| Open issues | 129 |
| Open pull requests | 97 |
| Releases | 75 |
| Latest release | 15.2.0 |
| Licence | Unlicense |
| Main language | Rust |
| Project age | 10 years |
| Last push | Nov 9, 2026 |
| Tracked files | 225 |
| Lines of code | 63.1K |
| Checkout size | 3 MB |
Lines by language: Rust 55.6K, Markdown 5,308, Shell 844, YAML 790, TOML 474, Ruby 24.
Questions
Is ripgrep free?
Yes. It is free and open source, dual-licensed under MIT or the Unlicense, with no paid version.
ripgrep or grep?
ripgrep for searching folders: it is usually much faster, searches subfolders by default and skips ignored, hidden and binary files. grep is installed everywhere and is fine for a single file or a pipe.
Does ripgrep work on Windows?
Yes, as a first-class platform. Install it with winget, Chocolatey or Scoop and run rg in PowerShell or Command Prompt.
Does ripgrep send my data anywhere?
No. It reads files on your computer and prints matches in your terminal. We found no network code.
How do I uninstall ripgrep?
Use the same package manager you installed it with: brew uninstall ripgrep, winget uninstall BurntSushi.ripgrep.MSVC or sudo apt remove ripgrep.
This post is part of GitHub Tools, where every repository is cloned and scanned before it is written up. The scan is a snapshot of one commit on one day; the repository has moved on since, so check it before you install.
