R Rubric

License & Disclaimer

Rubric is provided as-is, with no warranty. Use at your own risk.

This page is the human-readable summary of how Rubric is licensed and what that means for you. The full, legally binding license is reproduced on the License page and is also bundled as a LICENSE file with every install.

MIT, in plain English

Rubric is licensed under the MIT License. The short version:

  • You can use Rubric for anything — personal, commercial, evaluating job candidates, mock interviews with your team.
  • You assume the risk. There is no warranty, no fitness-for-purpose guarantee, and no liability on the authors. If Rubric eats your interview notes or drafts a report you wouldn’t have written, that’s on you.

The “no warranty” piece isn’t a formality — it’s the deal. Treat Rubric as a tool you trust the way you trust any other piece of software you didn’t build: cautiously, and with backups.

Rubric is distributed as binaries only; the MIT license terms apply to the binary distribution and its bundled assets. Source is not published.

Using Rubric in a hiring decision

A specific note for the most common use case: Rubric drafts a recommendation (Hire / No Hire / Follow Up) at the end of every session. The model is a drafting tool, not a decision-maker.

  • The interviewer is responsible for the recommendation, not the model.
  • Always read the draft before sharing it with anyone else.
  • Override anything that doesn’t reflect what you actually saw in the round.
  • Hiring decisions have real consequences for real people. The license disclaims liability; your professional and legal obligations to candidates do not.

If your organization has a formal policy on AI-assisted hiring decisions (and increasingly they do, depending on jurisdiction), make sure your use of Rubric falls within it.

Privacy summary

For the long version, see Settings and the relevant sections of Reports. The short version:

  • Rubric runs entirely on your machine. The project hosts no servers, runs no analytics, and proxies no requests.
  • AI features call the provider you configured (Anthropic or OpenAI) directly, with the relevant session payload. Read your provider’s data-use policies if that matters for your candidates.
  • Storage backends (local, git, S3) write whatever you generate to whatever location you configured. Sharing or restricting access is up to you.
  • Skip the API key if you want zero outbound calls.

Third-party notices

Rubric is built with the Flutter framework (BSD-3-Clause) and embeds a number of open-source packages, each under its own permissive license (typically MIT, BSD, or Apache 2.0). The principal direct dependencies:

  • flutter_riverpod — MIT (state management).
  • go_router — BSD-3-Clause (navigation).
  • flutter_markdown — BSD-3-Clause (Markdown rendering for the user guide and interviewer guides).
  • multi_split_view — MIT (the four-panel live-session layout).
  • webview_flutter — BSD-3-Clause (the embedded Excalidraw board).
  • hive — Apache 2.0 (local settings + session storage).
  • dio — MIT (HTTP client for Anthropic / OpenAI calls).
  • pdf, printing — Apache 2.0 (PDF report export).
  • google_fonts — Apache 2.0.
  • Typography: Source Serif 4, Inter, and JetBrains Mono under the SIL Open Font License.

A complete per-package listing is included in the THIRD_PARTY_NOTICES file bundled with each install.

Support & feedback

Bug reports, feature requests, and general feedback go through the support channel. Useful things to include in a bug report:

  • What you were doing when the bug happened (screen, interview, action).
  • What you expected vs. what actually happened.
  • Your platform (macOS / Windows / Linux) and Rubric version (shown on the Help screen).