@lerna/legacy-package-management

Legacy package management concerns provided by lerna. Please migrate to use npm/yarn/pnpm workspaces instead.

@lerna/legacy-package-management@8.2.4 was published on 2025-07-27. Its manifest declares 67 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=18.0.0.

Deprecated: In v9 of lerna, released in September 2025, the `lerna bootstrap`, `lerna add` and `lerna link` commands were finally fully removed after over 2 years of being deprecated. If you are still using these commands, please migrate to using your package manager's long-supported `workspaces` feature. You may find https://lerna.js.org/docs/legacy-package-management useful for this transition.

All @lerna/legacy-package-management versions · Permanent reference to 8.2.4

Package specifications

Version8.2.4
License declarationMIT
Published2025-07-27T18:10:21.538Z
Node.js requirement>=18.0.0
Type declarationsNot declared
Runtime dependency count67
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size321.07 KiB
Published file count95
Package typeNot declared
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies528
Repository stars36037
Repository forks2264

Install @lerna/legacy-package-management 8.2.4

npm install @lerna/legacy-package-management@8.2.4
pnpm add @lerna/legacy-package-management@8.2.4
yarn add @lerna/legacy-package-management@8.2.4

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review4/10 — Found 12/26 approved changesets -- score normalized to 4
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 29 commit(s) and 19 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
Pinned-Dependencies8/10 — dependency not pinned by hash detected -- score normalized to 8
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST5/10 — SAST tool is not run on all commits -- score normalized to 5

Evidence and freshness