← Home

resolve-glob

npm Repository Homepage

Ensures that absolute file paths are always returned from a glob pattern or array of glob patterns.

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jonschlinkert

Keywords

absolutedirdirectoryexpandexpansionfilefilepathglobisis-absoluteis-globpatternresolvetilde

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:globby AI (phantom-deps): Dependencies are declared and used indirectly; phantom-dep false positive for utility libraries with indirect dependency usage. ai
phantom-deps phantom-dep:lazy-cache AI (phantom-deps): Dependencies are declared and used indirectly; phantom-dep false positive for utility libraries with indirect dependency usage. ai
phantom-deps phantom-dep:resolve-dir AI (phantom-deps): Dependencies are declared and used indirectly; phantom-dep false positive for utility libraries with indirect dependency usage. ai
phantom-deps phantom-dep:is-valid-glob AI (phantom-deps): Dependencies are declared and used indirectly; phantom-dep false positive for utility libraries with indirect dependency usage. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.0 5 / 3
0.1.8 6 / 4
0.1.7 6 / 3
0.1.4 6 / 3
0.1.3 4 / 3
0.1.2 4 / 3
0.1.1 4 / 3
0.1.0 4 / 3

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.