Package Health Score

67 / 100

security
No known security issues
popularity
Influential project
maintenance
Inactive
community
Active

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
6.4.1	\|	01/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
6.3.0	\|	12/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.6.2	\|	10/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.0	\|	02/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.21.0	\|	05/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (642,774)

GitHub Stars: 35.74K
Forks: 2.26K
Contributors: 330

Direct Usage Popularity

The npm package @lerna/project receives a total of 642,774 downloads a week. As such, we scored @lerna/project popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @lerna/project, we found that it has been starred 35,745 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 330
Funding: No

A good and healthy external contribution signal for @lerna/project project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

Open Issues: 379
Open PR: 7
Last Release: 2 years ago
Last Commit: 1 month ago

Further analysis of the maintenance status of @lerna/project based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @lerna/project is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: ^14.15.0 || >=16.0.0

Age: 7 years
Dependencies: 13 Direct
Versions: 77
Install Size: 21 kB
Dist-tags: 2
# of Files: 8
Maintainers: 2
TS Typings: No

@lerna/project has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

`@lerna/project`

Lerna project configuration

Configuration Resolution

Lerna's file-based configuration is located in lerna.json or the lerna property of package.json. Wherever this configuration is found is considered the "root" of the lerna-managed multi-package repository. A minimum-viable configuration only needs a version property; the following examples are equivalent:

{
  "version": "1.2.3"
}

{
  "name": "my-monorepo",
  "version": "0.0.0-root",
  "private": true,
  "lerna": {
    "version": "1.2.3"
  }
}

Any other properties on this configuration object will be used as defaults for CLI options of all lerna subcommands. That is to say, CLI options always override values found in configuration files (a standard practice for CLI applications).

Command-Specific Configuration

To focus configuration on a particular subcommand, use the command subtree. Each subproperty of command corresponds to a lerna subcommand (publish, create, run, exec, etc).

{
  "version": "1.2.3",
  "command": {
    "publish": {
      "loglevel": "verbose"
    }
  },
  "loglevel": "success"
}

In the example above, lerna publish will act as if --loglevel verbose was passed. All other subcommands will receive the equivalent of --loglevel success (much much quieter).

@lerna/project dependencies

@lerna/package @lerna/validation-error cosmiconfig dedent dot-prop glob-parent globby js-yaml load-json-file npmlog p-map resolve-from write-json-file

FAQs

What is @lerna/project?

Lerna project configuration. Visit Snyk Advisor to see a full health score report for @lerna/project, including popularity, security, maintenance & community analysis.

Is @lerna/project popular?

The npm package @lerna/project receives a total of 642,774 weekly downloads. As such, @lerna/project popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @lerna/project well maintained?

We found indications that @lerna/project is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @lerna/project safe to use?

The npm package @lerna/project was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 23 November-2024, at 10:57 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

@lerna/project

Lerna project configuration For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (642,774)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Readme

`@lerna/project`

Configuration Resolution

Command-Specific Configuration

@lerna/project dependencies

FAQs

What is @lerna/project?

Is @lerna/project popular?

Is @lerna/project well maintained?

Is @lerna/project safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (642,774)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

@lerna/project

Configuration Resolution

Command-Specific Configuration

@lerna/project dependencies

FAQs

What is @lerna/project?

Is @lerna/project popular?

Is @lerna/project well maintained?

Is @lerna/project safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues

`@lerna/project`