← Home

@yarn-tool/ws-find-up-paths

在工作區環境中向上搜尋檔案或目錄的工具 (Find files or directories by walking up parent directories in workspace environments)

6
Versions
ISC
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

bluelovers

Keywords

yarnyarn-toolnpmpnpmlernaworkspacesmonorepofind-upfind-up-pathspath-searchparent-directoriesworkspace-rootpkgpackagepackagesdependenciesnode-modulesyarnlockcreate-by-yarn-tool

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established publisher with long track record; no provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dependency; phantom-dep false positive for TypeScript helper library. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.21 4 / 0
1.0.20 4 / 0
1.0.19 4 / 0
1.0.16 4 / 0
1.0.15 4 / 0
1.0.14 3 / 0

v1.0.21

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.

v1.0.19

1 finding
INFO No provenance attestation provenance

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

v1.0.16

1 finding
INFO No provenance attestation provenance

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

v1.0.15

1 finding
INFO No provenance attestation provenance

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

v1.0.14

1 finding
INFO No provenance attestation provenance

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