What we check
You can start before any models exist: setup guides, keyboard navigation, translation completeness, data cards and empty page states. Later come model regression tests, robustness checks and speed reports.
Time and a first task
Plan for about four hours a week. A first 30-minute step: follow one setup guide in a clean environment and note the first unstated requirement. Or go through one page of this website with the keyboard and describe a navigation problem.
Good first issues. If none fits, propose a check in a new issue.
A good bug report
- what you expected and the minimal steps to reproduce;
- environment and versions (only what is safe to publish);
- what happened – without guessing the cause;
- which checks were not run.
Use synthetic examples, never patient files or secrets. Report vulnerabilities through the security policy.