dependency-health

To check dependencies for risks, analyze your package.json and lockfiles to identify unused packages and overly permissive version ranges. This scoping ensures deterministic results by evaluating version ranges to flag potential dependency management issues.

Permissive versioning in npm dependencies uses broad version ranges that could lead to unexpected updates and potential risks. Detecting these broad ranges in your package.json helps maintain code health by preventing uncontrolled version changes.

Detect unused npm packages by analyzing your project dependencies scoped to package.json and lockfiles. Running this check before merging new features ensures newly added dependencies don't introduce bloat or unused packages into the codebase.

Yes, dependency risk analysis scopes its evaluation specifically to package.json and lockfiles to achieve deterministic results. This ensures the assessment of version ranges and unused packages is based on the exact locked dependency tree.

Analyzing project dependencies is limited to evaluating version ranges and identifying unused packages within the package.json and lockfiles. It does not execute code or resolve external security vulnerabilities beyond detecting permissive versioning risks.

The best way to perform a dependency health check is to analyze project dependencies by evaluating package.json and lockfiles together. This identifies unused packages and flags permissive versioning to maintain a healthier and more secure codebase.