micromatch
4.0.8 · 23 Aug 2024MIT222.4M / weekRepositorynpmAtom feed
Where each line stands
Plan an upgrade- 4.x4.0.8Safe from 4.0.8Latest line
- 3.x and older3.1.105 open advisories, worst moderate · last release Mar 2018, no longer updatedTo 4.0.8
Latest releases
All 69 releases- 4.x · latest line
4.0.8
23 Aug 2024Ultimate release that fixes both CVE-2024-4067 and CVE-2024-4068. We consider the issues low-priority, so even if you see automated scanners saying otherwise, don't be scared.
4.0.7
22 May 2024- Security
It is vulnerable to CVE-2024-4067
- Security
Updated braces to v3.0.3 to avoid CVE-2024-4068
This is basically v4.0.5, with some README updates
This is basically v4.0.5, with some README updates
- Security
It is vulnerable to CVE-2024-4067
- Security
Updated braces to v3.0.3 to avoid CVE-2024-4068
Does NOT break API compatibility
4.0.6
21 May 2024- Security
Fixes CVE-2024-4067
Added
hasBracesto check if a pattern contains braces.BREAKS API COMPATIBILITY
Added
hasBracesto check if a pattern contains braces.- Security
Fixes CVE-2024-4067
BREAKS API COMPATIBILITY
Should be labeled as a major release, but it's not.
Dependency tracking
Know when your own dependencies move
This page watches micromatch. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.