← Home

@lerna/version

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

Maintainers

jameshenrynrwlowner

Keywords

lernacommand

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@lerna/command AI (dependencies): First-party lerna sibling package, published in lockstep. ai
dependencies unvetted-dep:@lerna/github-client AI (dependencies): First-party lerna sibling package, published in lockstep. ai
dependencies unvetted-dep:@lerna/run-lifecycle AI (dependencies): First-party lerna sibling package, published in lockstep. ai
semgrep semgrep:dynamic-require AI (semgrep): Guarded local prettier require, not attacker-controlled input. ai
source-diff obfuscated-file-transition:dist/index.js AI (source-diff): Bundled build output with readable module manifest, not obfuscation; stable for this package. ai

Versions (showing 6 of 6)

Version Deps Published
6.6.2 1 / 0
6.6.0 1 / 0
6.5.1 1 / 0
6.5.0 1 / 0
6.1.0 27 / 0
6.0.2 27 / 0

v6.6.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.

v6.6.0

2 findings
HIGH Modified file became obfuscated: dist/index.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v6.5.1

1 finding
LOW No provenance attestation provenance

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

v6.5.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.

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

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