Is glob healthy, maintained, and safe?
Mostly yes — glob is maintained, with a couple of watch-items rather than red flags.
The verdict
OSPulse scores glob at 65/100 (low risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — glob is maintained, with a couple of watch-items rather than red flags.
The last release was 19 February 2026 (159 days ago); still within a normal window, but the cadence has quietened. Across 184 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 1 known advisory for glob, including 1 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
A couple of watch-items aside, glob is a reasonable dependency to rely on; keep an eye on the flagged signals. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (1)
glob CLI: Command injection via -c/--cmd executes matches with shell:true
Key facts
- Latest version
- v13.0.6
- Last release
- 19 February 2026 (159 days ago)
- Total releases
- 184
- First release
- 2 January 2011
- Package age
- 15.6 years
- Maintainers
- 1
- Known advisories
- 1
- Confidence
- High
Frequently asked
Is glob still maintained?
Partly — the most recent release was 19 February 2026 (159 days ago), so maintenance has slowed but not fully stopped.
Does glob have known security vulnerabilities?
Yes — OSV lists 1 advisory for glob. See the advisory list on this page for the OSV/GHSA identifiers.
Is glob safe to use?
Mostly yes — glob is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 65/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
glob is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-28 · scores are deterministic and recomputed on each refresh.