Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI engineers, coding-agent users, and software teams who want a coding agent to reason about code changes at the entity level (functions, classes, modules) instead of drowning in line-based diffs, because sem Ataraxy-Labs/sem ships semantic diffs, semantic blame, and impact analysis for 28 languages via tree-sitter, which means an agent can call sem diff and get back a structured
Where this stands now
Ataraxy-Labs/sem ranks #502 of 2195 tracked Radar items by composite score (8.0 against a section median of 6.2). The section currently carries 1090 Bronze, 646 Gold, 459 Silver. RepoRadar has retained observations for this record since 2026-06-22 (95 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 Ataraxy-Labs/sem if its scope or audience does not match what your team is building right now.
About this signal
Ataraxy-Labs/sem 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. Ataraxy-Labs/sem leads on novelty (10.0) and momentum (10.0); its lowest signal is setup ease (6.5), so factor that in before investing setup time. 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 Ataraxy-Labs/sem record combines a 8.0/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.
Putting this into practice? Read How to evaluate an AI tool before you adopt it 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.