| 1 | Short version for non-lawyers: |
| 2 | |
| 3 | The Rust Project is dual-licensed under Apache 2.0 and MIT |
| 4 | terms. |
| 5 | |
| 6 | It is Copyright (c) The Rust Project Contributors. |
| 7 | |
| 8 | Longer version: |
| 9 | |
| 10 | Copyrights in the Rust project are retained by their contributors. No |
| 11 | copyright assignment is required to contribute to the Rust project. |
| 12 | |
| 13 | Some files include explicit copyright notices and/or license notices. |
| 14 | For full authorship information, see the version control history or |
| 15 | <https://thanks.rust-lang.org> |
| 16 | |
| 17 | Except as otherwise noted, Rust is licensed under the Apache License, Version |
| 18 | 2.0 <LICENSE-APACHE> or <http://www.apache.org/licenses/LICENSE-2.0> or the MIT |
| 19 | license <LICENSE-MIT> or <http://opensource.org/licenses/MIT>, at your option. |
| 20 | |
| 21 | We track licenses for third-party materials in two ways: |
| 22 | |
| 23 | * We use [REUSE](https://reuse.software) to track license information for |
| 24 | in-tree source files - both those authored by the Rust project and those |
| 25 | authored by third parties. See `REUSE.toml`, and our cached output of the |
| 26 | `reuse` tool which is committed to `license-metadata.json`. |
| 27 | * We use `cargo` to track license information for out-of-tree dependencies. |
| 28 | |
| 29 | These two sources of information are collected by the tool `generate-copyright` |
| 30 | into a file called `COPYRIGHT.html`, which is shipped with each binary release |
| 31 | of Rust. Please refer to that file for detailed information as to the components of |
| 32 | any given Rust release. We also produce a `COPYRIGHT-library.html` file which only |
| 33 | covers the subset of source code used in the Rust Standard Library, as opposed |
| 34 | to the toolchain as a whole. |