Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI engineers, agent builders, platform teams, and coding-agent power users who want a package-manager-style install path for MCP servers and reusable agent skills instead of cloning dozens of repos or hand-curating ~/.claude/skills, because apm microsoft/apm from Microsoft ships a registry format, versioned manifests, deterministic installs, and a single CLI that integrates with
Where this stands now
microsoft/apm ranks #233 of 2143 tracked Radar items by composite score (8.4 against a section median of 6.7). The section currently carries 1038 Bronze, 646 Gold, 459 Silver. RepoRadar has retained observations for this record since 2026-06-22 (94 days in the current window). Signal extremes versus the section: momentum at the 97th percentile; novelty at the 97th percentile.
Who should use it
Who should skip it
Pass on microsoft/apm if its scope or audience does not match what your team is building right now.
About this signal
microsoft/apm is tracked by RepoRadar as a developer tool in the Radar section. First seen 2026-06-22; the source record was last checked on 2026-06-22. The current verdict is 'try now' with a Gold tier and review needed setup difficulty. Across RepoRadar's eight signals, microsoft/apm is strongest on novelty (10.0) and momentum (10.0) and weakest on setup ease (6.5) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The microsoft/apm record combines a 8.4/10 composite score with separate popularity (100.0), risk (low), and setup (review needed) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
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
Risk label is still being reviewed from the captured evidence. Treat the item as unknown-risk until you review the linked source, permissions, setup path, and data access.