Research prototype with solid docs and examples, but opaque setup and rougher-than-it-should-be onboarding will slow newcomers down.
The rubric
First Glance
78Clear what USE does (UML/OCL model validation), but the research-prototype disclaimer and missing homepage limit credibility.
Reasoning available in the full report.Onboarding Runway
55Installation instructions exist but are vague, and the example walkthrough requires multiple manual steps with insufficient error guidance.
Reasoning available in the full report.Core Payoff
72The tool delivers its core promise (model validation with OCL) via clear examples, but reaching the payoff requires getting past opaque setup.
Reasoning available in the full report.Trust Signals
75Extensive manual with screenshots, test files referenced, and academic references present; but no visible test suite, no recent release notes, and unclear maintenance status.
Reasoning available in the full report.Friction Feel
61Documentation gaps, path assumptions, and a vague system-requirements list create small but cumulative papercuts.
Reasoning available in the full report.Signs of Life
65CI/CD workflows present and recent commit timestamp, but research-grade maintenance signals and 30 unresolved issues suggest limited active support.
Reasoning available in the full report.
Where the grip slips
6 more issues found โ each with a concrete fix.
Unlock the full report
See all 7 issues with concrete fixes and the reasoning behind every score. One-off, tied to your account so it works on every device โ sign in with GitHub to buy. The score and badge stay free.
Show your score
[](https://latch.fyi/useocl/use)Share this analysis
https://latch.fyi/useocl/useFixed some issues? Re-analyze to measure your progress โ
Copy the whole report
Grab the entire verdict in one go โ a Markdown block for a README or an issue, plain text, or a prompt you can paste straight into an LLM.