Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who already juggle several model providers and want a reusable way to compare or fuse them inside the same agent workflow instead of manually re-running prompts across separate tools.
Who should use it
Who should skip it
Consider hashangit/openfusion lower priority if you already have a working solution in this category.
About this signal
hashangit/openfusion is tracked by RepoRadar as a developer tool in the Agent Runtime section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, hashangit/openfusion is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on maturity (5.8) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. 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 hashangit/openfusion 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 1.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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
It routes the same prompt across multiple external model providers, so review provider retention and data-handling before sending proprietary repository context; Fused answers can make provenance harder to inspect than a single-model run, so keep a baseline path for debugging, evaluation, and cost checks.