fast-glob
It's a very fast and efficient glob library for Node.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:bash-glob | AI (dependencies): bash-glob is a legitimate dependency for a glob implementation; stable and expected for this package's functionality. | ai | |
| dependencies | unvetted-dep:readdir-enhanced | AI (dependencies): readdir-enhanced is a legitimate enhanced directory reader dependency; appropriate for a glob library and stable across versions. | ai | |
| dependencies | unvetted-dep:@mrmlnc/readdir-enhanced | AI (dependencies): @mrmlnc/readdir-enhanced is the same author's own scoped package, a natural internal dependency for fast-glob; no malicious signal. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): picomatch is an established glob library; adding it reflects a legitimate refactoring to use @nodelib ecosystem for filesystem operations. | ai | |
| dependencies | unvetted-dep:@nodelib/fs.walk | AI (dependencies): @nodelib packages are established ecosystem components; constraint ^1.2.3 is stable and appropriate for a glob library. | ai | |
| provenance | no-provenance | AI (provenance): Historical limitation; package has clean repository and no malware indicators. Provenance is a future improvement, not a blocker. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.3.3 | 5 / 21 | |
| 3.3.2 | 5 / 21 | |
| 3.3.1 | 5 / 21 | |
| 3.3.0 | 5 / 21 | |
| 3.2.12 | 5 / 29 | |
| 3.2.11 | 5 / 29 | |
| 3.2.10 | 5 / 29 | |
| 3.2.9 | 5 / 29 | |
| 3.2.8 | 5 / 29 | |
| 3.2.7 | 5 / 29 | |
| 3.2.6 | 5 / 29 | |
| 3.2.5 | 6 / 28 | |
| 3.2.4 | 6 / 28 | |
| 3.2.3 | 6 / 28 | |
| 3.2.2 | 6 / 25 | |
| 3.2.1 | 6 / 25 | |
| 3.2.0 | 5 / 25 | |
| 3.1.1 | 5 / 25 | |
| 3.1.0 | 5 / 25 | |
| 3.0.4 | 6 / 27 | |
| 3.0.3 | 6 / 27 | |
| 3.0.2 | 6 / 27 | |
| 3.0.1 | 6 / 27 | |
| 3.0.0 | 6 / 27 | |
| 2.0.3 | 4 / 26 | |
| 2.0.2 | 4 / 26 | |
| 2.0.1 | 4 / 26 | |
| 2.0.0 | 4 / 25 | |
| 1.0.1 | 4 / 11 | |
| 1.0.0 | 4 / 11 |
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.