Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for operators who want a real local orchestration layer for agent workflows, but it needs a careful first review because the whole point is connecting agents to live accounts and scheduled tasks.
Who should use it
Who should skip it
Avoid running muratgur/ordinus in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
muratgur/ordinus is tracked by RepoRadar as a tool / platform in the Agent Orchestration section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'worth watch' with a Silver tier and advanced setup difficulty. muratgur/ordinus leads on workflow potential (8.7) and open-source/build quality (8.4); its lowest signal is setup ease (4.2), so factor that in before investing setup time. 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 muratgur/ordinus 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 'medium' 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 is designed to connect agents to live email, messaging, social, project, and observability accounts, so first evaluation should use test accounts with send-capable actions disabled; Unsigned desktop builds and scheduled workflow execution raise the blast radius of a bad configuration, so review permissions and launch provenance before broader use.