← Home

@yarn-tool/fix-ws-pkgs-link

```bash yarn add @yarn-tool/fix-ws-pkgs-link yarn-tool add @yarn-tool/fix-ws-pkgs-link yt add @yarn-tool/fix-ws-pkgs-link ```

11
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

yarnyarn-toolnpmlernaworkspacespkgdependenciesmonorepoyarnlocknode-modulespackagespackage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established publisher with clean track record; no provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is declared as a runtime dep in package.json; phantom-dep false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
3.0.12 8 / 0
3.0.11 8 / 0
3.0.10 8 / 0
3.0.9 8 / 0
3.0.6 8 / 0
3.0.5 8 / 0
3.0.4 8 / 0
3.0.3 8 / 0
3.0.2 8 / 0
3.0.1 8 / 0
3.0.0 8 / 0

v3.0.2

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.

v3.0.1

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.

v3.0.0

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.