[260912] Say No to Abandoned Projects! See the Full Picture at a Glance | x-cmd v0.10.9

X-cmd released v0.10.9, adding project health reports to the `x install` command that surface Stars, OpenSSF Scorecard ratings, and activity over 30, 60, 90, 180, and 360 days to flag unmaintained open-source tools. The reports cover 2,500+ projects with data updated daily and cached for 1 day, and `x repo card` now tracks 60-day, 720-day, and total historical metrics plus physical line-of-code counts. The release also updates `x cpu` to separate Apple Silicon P-cores and E-cores and adds GLM and MiniMax model support to `x codex`.

Say No to Abandoned Projects See the Full Picture at a Glance | x-cmd v0.10.9 TLDR - x install Project Health Reports : Preview Stars, OpenSSF scores, and 30–360 day activity Commits, PRs, Issues via --report , --info , or fzf pane to avoid unmaintained tools. - Data & Coverage : Covers 2,500+ projects updated daily, with 1-day caching to minimize GitHub API calls. - Expanded Repo Metrics : x repo card adds 60-day, 720-day, total historical stats, and physical line-of-code counts. - Hardware & AI Upgrades : x cpu now separates Apple Silicon P-cores and E-cores; x codex adds GLM and MiniMax models. You pick an open-source tool with a decent Star count and excitedly run brew install . After using it for a while, you notice: Hundreds of unaddressed issues are piling up, the latest commit was made a year or two ago, and the Releases page has stalled on a very old version. The software is installed, but the project itself is practically dead. The recently released x-cmd v0.10.9 adds a project health report directly into x install . Check the Project Report Before Installing Run directly: x install --report jq To view the project report for jq. It currently displays Stars, Forks, Releases, PRs, Issues, Commits, and recent activity levels over the past 30, 60, 90, 180, and 360 days. It also includes the OpenSSF Scorecard, programming languages, lines of code, project creation date, latest commit, and latest release information. When evaluating software, you won't just see how many Stars it has, but also whether there have been recent Commits, PRs, Issues, and Releases . Part of this data originates from x repo card. View Installation Methods and Project Status Together If you want to view installation methods alongside project health, use: x install --info jq The top section shows installation methods, while the bottom section displays the project report. For instance, installation methods might include: brew install jq apt install jq x pkg use jq x eget jqlang/jq x asdf use jq Followed by project metrics such as Stars, Scorecard, and Commits, PRs, and Releases over various timeframes. Direct Preview inside fzf When using the interactive x install fzf menu, the right-hand preview pane automatically displays the project report . Move your cursor over any software, and the corresponding activity metrics and scores appear on the right. Reports are cached for 1 day to avoid repeatedly fetching from GitHub raw. It currently covers 2,500+ open-source software projects with data updated daily . Expanded Time Ranges in x repo card To make project report data more complete, x repo card has expanded its tracking to include 60-day, 720-day, and total metrics. Where you previously could view 30, 90, 180, and 360 days, you can now look back up to 720 days, as well as cumulative data since project creation . Physical line counts have also been added to track the actual codebase size in the workspace. All of this data feeds into the project reports. Other Updates x cpu can now differentiate between E-cores and P-cores on Apple Silicon , displaying the idle rates for both core clusters. x codex added support for GLM and MiniMax models . If you plan to install an open-source CLI tool soon, give it a try: x install If there is a project you would like to inspect or additional metrics you'd like to see, feel free to leave a comment or submit a PR. Please indicate the source and link of this article when reprinting. Help us make these docs great All X-CMD docs are generated from command help and multiple data sources. See something that's wrong or unclear? Feel free to let us know through any of these ways~