← Home

@yarn-tool/find-root

npm Repository Homepage

尋找 Yarn workspace 根目錄的工具，提供路徑驗證、錯誤處理和斷言函數 (Find Yarn workspace root directory with path validation, error handling, and assertion functions)

21
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bluelovers

Keywords

monorepoworkspace-rootfind-rootpkg-dirpackage-rootroot-directorypath-validationworkspacesyarnyarn-toolnpmpnpmlernaassertion

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@ts-type/package-dts AI (phantom-deps): @ts-type/package-dts is a type-declaration package used in config/type files, not directly imported at runtime — stable false positive. ai

Versions (showing 21 of 21)

Version Deps Published
2.0.24 7 / 0
2.0.23 7 / 0
2.0.21 7 / 0
2.0.17 7 / 0
2.0.16 7 / 0
2.0.15 7 / 0
2.0.14 7 / 0
2.0.13 7 / 0
2.0.12 7 / 0
2.0.11 7 / 0
2.0.10 7 / 0
2.0.9 7 / 0
2.0.8 7 / 0
2.0.7 7 / 0
2.0.6 7 / 0
2.0.5 7 / 0
2.0.4 7 / 0
2.0.3 7 / 0
2.0.2 7 / 0
2.0.1 7 / 0
2.0.0 6 / 0

v2.0.14

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.

v2.0.13

1 finding
LOW No provenance attestation provenance

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

v2.0.12

1 finding
LOW No provenance attestation provenance

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

v2.0.11

1 finding
LOW No provenance attestation provenance

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

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.9

1 finding
LOW No provenance attestation provenance

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

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.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.

v2.0.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.