dir-glob
Convert directories to glob compatible strings
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:path-type | AI (dependencies): path-type is a well-known, minimal utility from the same trusted ecosystem (sindresorhus/kevva); no security concerns associated with it. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from kevva to sindresorhus is a known legitimate maintainer transition. Sindresorhus is a highly trusted npm publisher with 355 packages and 2256 approved versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sindresorhus added as maintainer is a well-known legitimate ecosystem handoff; no compromise indicators present. | ai | |
| provenance | no-provenance | AI (provenance): dir-glob is a long-established package (2488 days); lack of provenance is expected for packages predating Sigstore adoption and poses no real risk here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 1 / 5 | |
| 3.0.0 | 1 / 5 | |
| 2.2.2 | 1 / 5 | |
| 2.2.1 | 1 / 5 | |
| 2.2.0 | 1 / 5 | |
| 2.0.0 | 2 / 5 | |
| 1.1.0 | 3 / 4 | |
| 1.0.2 | 3 / 4 | |
| 1.0.1 | 3 / 4 | |
| 1.0.0 | 3 / 4 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2019-06-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
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.2.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.2.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.
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.1.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.2
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.