raineorshine/npm-check-updates

Features

• Package Dependency Managers - Checks for newer versions of npm packages and updates project manifest files to the latest releases.
• Outdated Version Detection - Identifies updates for dependencies that exceed the version ranges specified in the project manifest.
• Package Registry Integrations - Retrieves the latest package versions by querying a remote package registry or local JSON mirrors.
• Manifest-Driven Dependency Managers - Parses project configuration files to compare installed dependency versions against remote registry data.
• Automated Dependency Updaters - Identifies newer versions of dependencies and updates the manifest files according to selected target rules.
• Recursive Manifest Scanning - Scans the working directory for all manifest files to update dependencies across multiple projects simultaneously.
• Package Registry Clients - Fetches package version data from the npm registry or custom JSON files to identify available updates.
• Package Upgraders - Upgrades versions in a package file to the latest available releases while preserving semantic versioning policies.
• Semver Constraint Filtering - Filters potential updates using semantic versioning rules to restrict upgrades to specific ranges like patches or minors.
• Version Constraints - Allows restricting version upgrades to specific semantic ranges, such as only applying patches or minor updates.
• Dependency Analysis - Identifies outdated dependencies by comparing current versions against the latest available versions in a registry.
• Semantic Versioning Systems - Upgrades package constraints to the latest releases while strictly respecting semantic versioning rules.
• Supply Chain - Implements security mechanisms to mitigate supply chain attacks by filtering unstable or malicious new releases.
• Recursive Manifest Scanning - Traverses the directory tree to find and update multiple manifest files across monorepos or complex project structures.
• Monorepo Dependency Auditing - Identifies outdated dependencies and checks for new releases across multiple projects in a workspace.
• Manifest File Discovery - Traverses the file system to locate and update multiple manifest files across a monorepo structure.
• Package Selection Filters - Uses regular expressions and wildcards to include or exclude specific packages or organization scopes from the update process.
• Update Execution APIs - Provides a programmatic interface allowing developers to execute dependency checks and upgrades within custom scripts.
• Dependency Scope Targeting - Limits update checks to specific sections of the manifest, such as production or development dependencies.
• Dependency Update Cooldowns - Prevents the adoption of new versions by requiring they meet a minimum publication age to ensure stability.
• Programmatic Update APIs - Provides a programmatic module for integrating version check and upgrade logic into automated workflows.
• Update Candidate Filtering - Includes or excludes specific packages from the update process using strings, regex, or custom functions.
• Update Exclusion Filters - Provides flags and filters to prevent specific dependencies from being updated in the project manifest.
• Interactive Update Selection - Provides a user interface to manually choose which specific dependencies should be upgraded.
• Iterative Test Execution - Installs updates and runs test suites sequentially to identify which specific package change causes a build failure.
• Provenance Tracking - Verifies if the publisher of a package has changed between versions to detect potential account takeovers.
• Release Cooldowns - Prevents the adoption of very recent releases by requiring a minimum publication age to ensure stability.
• Package Scope Filtering - Uses wildcards or regular expressions to filter updates for specific packages and organization scopes.
• Dependency Aliasing - Resolves and updates dependency versions specified via GitHub URLs or package aliases.
• Version and Compatibility Management - Ensures updated packages remain compatible with the peer dependency constraints of other installed modules.
• Supply Chain Security - Mitigates supply chain risks by preventing the adoption of very recent, potentially unstable or malicious releases.
• Software Supply Chain Security - Protects the development pipeline by filtering out very recent releases to avoid unstable or compromised packages.
• Distribution Tag Targeting - Selects the upgrade version based on criteria such as distribution tags or specific release tags.
• Update Regression Testing - Installs upgrades and runs tests iteratively to identify which specific package update causes a build or test failure.
• Package Management - Checks for dependency updates.

Star history