upstream-backport vs github-copilot-modernization
upstream-backport is a plugin bundle for AI coding tools published by JZ Loh. Marketplaces we read that list it: 1 (Community GitHub marketplaces). github-copilot-modernization is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace bitshelf/linux-skills | Not seen in the last pass Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 1.24.0 Forks (GitHub): 15 Stars (GitHub): 53 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | upstream-backport | github-copilot-modernization |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 53 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 15 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.deepwiki.com/mcp) | Installs as a plugin bundle |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 8 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bitshelf/linux-skills | github.com/microsoft/github-copilot-modernization |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 20 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
upstream-backport
免克隆取证 + 五阶段 backport 工作流(Buildroot/Yocto/AOSP/Debian/内核)
github-copilot-modernization
Autonomous application modernization using multi-agent orchestration for GitHub Copilot CLI. Supports Java upgrades (8→21, Spring Boot 2.x→3.x), .NET modernization, Azure migration, CVE/vulnerability fixing, and application rearchitecture (monolith-to-microservices). Features a 3-level agent hierarchy (orchestrator → coordinators → executors) with enterprise rulebook support for embedding organizational policies into the workflow.
How to run each
upstream-backport As a Claude Code plugin
/plugin marketplace add bitshelf/linux-skills
/plugin install upstream-backport@embedded-backport-tools
github-copilot-modernization
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only upstream-backport has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: upstream-backport · What it can do: github-copilot-modernization · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.