Compatibility

Source and License FAQ

Component terms, the historical Rust reference and permanently retained releases.

Can I use Topaz commercially?

Yes. The executable grant covers commercial use, automated builds and hosted services. Public source components use Apache-2.0. Keep the notices required for components you redistribute.

Can I read the complete Rust compiler?

The complete 5.20.4 Apache snapshot remains in its historical source browser and source archive. From 5.21.0, new public distributions contain authorized Topaz source components. New company-owned Rust originals remain private.

Did earlier Apache rights change?

No. Existing Apache grants and third-party rights remain effective. Previously published Apache code does not become proprietary under this policy.

Does the npm license cover its downloaded executable?

The wrapper uses Apache-2.0. Its downloaded executable carries separate binary terms and component licenses.

Must I publish programs I create?

The executable and generated-output grants do not require publication of your Topaz source. Included runtimes and third-party code retain their own notices and licenses.

Where are older releases and 5.21?

The official download list starts at 5.20.4. Actually published artifacts from that version onward are retained permanently. Earlier versions are outside this commitment; rights in received copies remain. The manual describes 5.21, while the download manifest identifies actually available files.

Read Licenses and Public Source for the archive, hash and component terms.