RVLTION Download

Licenses

What RVLTION is built on.

Counted from the dependency tree rather than written by hand. The figures below are for a Windows build, which is the only platform whose tree has been resolved.

RVLTION itself

RVLTION is proprietary. Copyright RVLTION, all rights reserved. The RVLTION brand owns the source code, the user interface and product design, the documentation, this website and the RVLTION name and branding.

No public license is granted to that material. Reproduction, modification and distribution each require prior written authorisation. No source repository is published. See the legal page.

Everything else on this page is third-party material. It is not owned by RVLTION, and each component keeps its own license, unaffected by the paragraph above.

Backend dependencies

284 crates resolve for a Windows build, including transitive dependencies. Their licenses break down as follows.

LicenseCrates
MIT or Apache-2.0, either155
MIT only52
Unicode-3.018
Unlicense or MIT10
MPL-2.05
Zlib variants5
BSD-3-Clause variants4
BSL-1.03
Apache-2.0 only2
Other permissive combinations30

All are permissive. The five MPL-2.0 components are file level copyleft, which is satisfied by using them unmodified.

Interface dependencies

Four runtime dependencies, which is the entire list.

PackageVersionLicense
react19.2.8MIT
react-dom19.2.8MIT
zustand5.0.15MIT
@tauri-apps/api2.11.1Apache-2.0 or MIT

Notable components

  • Tauri, Apache-2.0 or MIT. The desktop application framework.
  • SQLite, public domain, compiled in through rusqlite rather than linked from the system so the behaviour is identical everywhere.
  • WebView2 on Windows, supplied by the operating system under Microsoft terms and not redistributed by RVLTION.
  • arboard, MIT or Apache-2.0, used for clipboard access on macOS and Linux only.

Getting the full list

The complete resolved tree, with every crate and version, comes from the workspace itself.

cargo tree --manifest-path src-tauri/Cargo.toml --edges normal

The figures on this page were produced with cargo metadata filtered to the Windows target. A different platform resolves a slightly different set, so these counts describe a Windows build specifically.