@vscode/ripgrep

A module for using ripgrep in a Node project

@vscode/ripgrep@1.18.0 was published on 2026-05-07. Its manifest declares 12 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @vscode/ripgrep versions · Permanent reference to 1.18.0

Package specifications

Version1.18.0
License declarationMIT
Published2026-05-07T16:32:36.128Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count12
Peer requirement count0
Optional dependency count12
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size4.27 KiB
Published file count5
Package typemodule
ES module entryNot declared
Default entry./lib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies12
Repository stars205
Repository forks66

Install @vscode/ripgrep 1.18.0

npm install @vscode/ripgrep@1.18.0
pnpm add @vscode/ripgrep@1.18.0
yarn add @vscode/ripgrep@1.18.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review10/10 — all changesets reviewed
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License9/10 — license file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
SAST4/10 — SAST tool is not run on all commits -- score normalized to 4

Evidence and freshness