@automattic/effective-module-tree

v0.1.0

A tool to generate the effective list of dependencies of any project For more information about how to use this package see README

Latest version published 5 years ago

License: GPL-2.0

NPM

GitHub

Package Health Score

70 / 100

security
No known security issues
popularity
Small
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

All Versions

Version				Vulnerabilities	License Risk
0.1.0	\|	04/2020	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.0.1	\|	03/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

GPL-2.0

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.

Security Policy

Yes

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

Small

Weekly Downloads (2)

GitHub Stars: 12.43K
Forks: 1.99K
Contributors: 350

Direct Usage Popularity

The npm package @automattic/effective-module-tree receives a total of 2 downloads a week. As such, we scored @automattic/effective-module-tree popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @automattic/effective-module-tree, we found that it has been starred 12,426 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: 350
Funding: No

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

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 5.11K
Open PR: 660
Last Release: 5 years ago
Last Commit: 2 months ago

Further analysis of the maintenance status of @automattic/effective-module-tree 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 @automattic/effective-module-tree 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

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: not defined

Age: 5 years
Dependencies: 3 Direct
Versions: 3
Install Size: 30.2 kB
Dist-tags: 1
# of Files: 9
Maintainers: 59
TS Typings: No

@automattic/effective-module-tree 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

effective-module-tree

CLI tool that generates an ASCII tree with the representation of packages in node_modules and their dependencies. This works over the actual node_modules files, so you need to install your dependencies first (i.e. npm install or yarn install).

It generates the logical representation of the tree. A package may appear multiple times if it is depended on by multiple packages, even if all point to the same file on the filesystem. In other words, it "un-hoist" hoisted/deduped packages.

Why?

Usually, the package manger has a way to list the dependencies (npm ls or yarn list). However this includes deduplicated packages, and requires the presence of the lock file to generate the tree. This is the package manager's vision of the tree.

System tools like ls, find or tree can generate a similar output, but those represent the filesystem view of the tree. Depending on how effective the package manager is hoisting dependencies, this view may not be comparable.

effective-module-tree generates node's vision of the dependency tree. Is what node will find when requiring dependencies, ignoring where the package physically live in the file system. This tree should be consistent across package managers and different hoisting capabilities. As such, it can be used to verify that the dependeny tree remains constant when migrating to a different package manager.

Usage

Run effective-module-tree in the root of your project.

Use `effective-module-tree --root

@automattic/effective-module-tree dependencies

debug yargs object-treeify

FAQs

What is @automattic/effective-module-tree?

A tool to generate the effective list of dependencies of any project. Visit Snyk Advisor to see a full health score report for @automattic/effective-module-tree, including popularity, security, maintenance & community analysis.

Is @automattic/effective-module-tree popular?

The npm package @automattic/effective-module-tree receives a total of 2 weekly downloads. As such, @automattic/effective-module-tree popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @automattic/effective-module-tree well maintained?

We found indications that @automattic/effective-module-tree is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @automattic/effective-module-tree safe to use?

The npm package @automattic/effective-module-tree 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 11 December-2024, at 21:34 (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