Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Codex users who want to route the CLI through alternative providers without waiting for every upstream API mismatch to be solved first.
Who should use it
Who should skip it
Skip Cmochance/codex-app-transfer if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
Cmochance/codex-app-transfer is tracked by RepoRadar as a developer tool in the AI Gateway section. It was first seen on 2026-06-19 and last updated on 2026-06-19. The current verdict is 'watch' with a Silver tier and moderate setup difficulty. The standout signals for Cmochance/codex-app-transfer are open-source/build quality (8.4) and workflow potential (8.3), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Cmochance/codex-app-transfer a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 69.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Codex App Transfer handles prompts and provider credentials on the local gateway path, so review logging and secret handling before routing private code through it; The README says only Kimi For Coding and Xiaomi MiMo received end-to-end real-world testing, so treat other provider routes as less verified until you test them yourself.