@lage-run/globby
3
Versions
—
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
microsoft1eskenotron_msftecraig12345_msft
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process use is from bundled unicorn-magic dependency (execFile for glob operations), not malicious. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo utility; missing README/repo/keywords expected for scoped ecosystem packages. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Intentional wrapper of globby under the @lage-run/ monorepo scope; not a typosquat. | ai |
v14.2.2
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.
v13.0.2
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.
v13.0.1
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.