upstream-backport vs Qodo
upstream-backport is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
upstream-backport is a plugin bundle for AI coding tools published by JZ Loh. No marketplace we read lists it any more. Qodo is a plugin bundle for AI coding tools published by qodo-ai. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Qodo | |
|---|---|---|
| Community marketplace bitshelf/linux-skills | Removed on 2026-10-15 Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Codex: openai-curated (openai/plugins) | Not listed | Listed Version: 2.1.2 Forks (GitHub): 8 Stars (GitHub): 57 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-backportno longer listed · | Qodo |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 57 |
| Forks (GitHub) (differs) | 0 | 8 |
| Last release (differs) | Not published | 2026-10-15 |
| 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 | 5 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bitshelf/linux-skills | github.com/qodo-ai/qodo-skills |
| Changes in the last 7 days (differs) | 4 | 3 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of upstream-backport
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Source-first URL clone, capture, bounded rebuild, and fidelity verification workflow.
-
ultrapack — lean, opinionated skill pack for spec-driven, git-centered development
-
You found a plugin that makes your coding agent actually good. One thing bothers you. So you fork it and change it. Three weeks later, upstream ships a release with fixes you…
-
okl — Observed Knowledge Ledger
Lessons your coding agent can trust: briefed before each task, proven by checks, flagged on change.
-
Bundles the musts skill and a PreToolUse hook that runs `musts validate` before each `git commit` and blocks it until the loop is clean.
-
Version tracking for Agent Skills bundles across sessions, surfaces, and platforms. When you load a skill into a new session, Skill Provenance reads the manifest, verifies file…
What each says it does
upstream-backport
免克隆取证 + 五阶段 backport 工作流（Buildroot/Yocto/AOSP/Debian/内核）
Qodo
Qodo setup, code intelligence, and review workflows.
How to run each
upstream-backport
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Qodo As a Codex plugin
codex plugin marketplace add openai/pluginsCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: Qodo · 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/openai/plugins/blob/HEAD/.agents/plugins/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.