Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Use AgentScope when you need structured handoffs, reusable agent primitives, and observable orchestration instead of ad-hoc scripts.
Who should use it
Who should skip it
Move on from agentscope-ai/agentscope if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
agentscope-ai/agentscope is tracked by RepoRadar as a developer tool in the AI Agent Framework section. It was first seen on 2026-06-18 and last updated on 2026-06-18. The current verdict is 'try now' with a Gold tier and advanced setup difficulty. The standout signals for agentscope-ai/agentscope are workflow potential (10.0) and practical usefulness (9.0), while setup ease (4.2) 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 agentscope-ai/agentscope a composite score of 9.2 out of 10, placing it in the Gold 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 92.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
Agent runtimes can call external APIs and services; constrain credentials per tool and enforce idempotency for retries; Advanced orchestration patterns have a steeper onboarding curve than single-agent wrappers.