A simple measure of software dependency freshness
A simple measure of dependency freshness
A simple measure of dependency freshness
Track your dependency drift across multiple repositories using libyear.
A simple measure of software dependency freshness
A high-performance [libyear](https://libyear.com/) dependency debt analyzer for large scale usage across an entire organization.
Scan npm dependencies for abandoned packages, outdated versions (libyear), and known CVEs (OSV.dev). Health scores 0-100, SARIF for GitHub Code Scanning, zero dependencies.
A simple measure of software dependency freshness
Prioritize npm package updates by importance and risk. See which outdated packages matter and which are safe to update.
Runs ESLint on changed files
CLI tool to analyze dependency evolution and release frequency
A simple measure of software dependency freshness
The all-seeing repository analyzer
A simple measure of dependency freshness
A simple measure of software dependency freshness
libyear-rb analyzes your Gemfile.lock and tells you how out-of-date your dependencies are, in libyears (the time between your installed version and the newest version).
Analyses your Gemfile for dependency health: checks if gems are actively maintained (last commit dates via GitHub and GitLab, release dates), outdated versions, archived repos, OpenSSF Scorecard security scores, known vulnerabilities via deps.dev, and libyear drift. Ruby version freshness with EOL detection. Handles rubygems, git, path, and GitHub Packages sources. Outputs coloured terminal tables, markdown, or JSON. CI quality gates with --fail-if-critical, --fail-if-warning, --fail-if-vulnerable, --fail-if-outdated, and --ignore. A comprehensive alternative to running bundle outdated, bundler-audit, and libyear-bundler separately.
No description provided.
No description provided.