# What License Governs Supertonic? Understanding the MIT License Terms

> Discover the MIT License terms governing Supertonic. Use, modify, and distribute this project freely across commercial and open-source applications with ease.

- Repository: [Supertone Inc./supertonic](https://github.com/supertone-inc/supertonic)
- Tags: licensing
- Published: 2026-06-13

---

**Supertonic is released under the permissive MIT License, allowing free use, modification, and distribution across commercial and open-source projects with minimal attribution requirements.**

Supertonic, developed by Supertone Inc. and hosted in the `supertone-inc/supertonic` repository, is governed by the MIT License. This permissive open-source license ensures the audio processing library can be integrated into projects spanning multiple programming languages—including C++, Rust, Swift, Python, and Java—while maintaining clear attribution requirements.

## What License Does Supertonic Use?

The Supertonic repository explicitly declares the **MIT License** as its governing legal framework. The complete license text resides in the repository root at `LICENSE`, establishing the terms under which the code can be used, modified, and redistributed according to the `supertone-inc/supertonic` source code.

## MIT License Permissions and Obligations

The MIT License grants broad rights with minimal restrictions, making it ideal for cross-platform audio libraries.

### Usage Rights

According to the `LICENSE` file, the MIT License permits users to:

- **Use** the software for any purpose, including commercial applications
- **Copy** and **distribute** original or modified versions
- **Modify** the code and create derivative works
- **Sublicense** the software, including it in proprietary products

### Attribution Requirements

The only obligations under the Supertonic license require preserving the copyright notice, permission notice, and license text in all copies or substantial portions. The license also disclaims warranties, stating the software is provided "as is" without any liability to the authors.

## How the MIT License Appears Across Supertonic Bindings

The MIT license declaration propagates consistently across all language bindings and build system configurations in the repository, ensuring uniform licensing regardless of integration method.

In the Node.js bindings, [`nodejs/package.json`](https://github.com/supertone-inc/supertonic/blob/main/nodejs/package.json) explicitly declares:

```json
"license": "MIT"

```

For Python distributions, [`py/pyproject.toml`](https://github.com/supertone-inc/supertonic/blob/main/py/pyproject.toml) specifies:

```toml
[project]
license = {text = "MIT"}

```

The Rust crate defines it in [`rust/Cargo.toml`](https://github.com/supertone-inc/supertonic/blob/main/rust/Cargo.toml):

```toml
license = "MIT"

```

Java modules reference it in [`java/pom.xml`](https://github.com/supertone-inc/supertonic/blob/main/java/pom.xml):

```xml
<licenses>
  <license>
    <name>MIT License</name>
  </license>
</licenses>

```

## Practical Implementation Examples

When integrating Supertonic into your projects, include the MIT license identifiers as demonstrated in the source files.

*Adding the MIT license header to a new source file (C++ example)*:

```cpp
// SPDX-License-Identifier: MIT
// Copyright (c) 2025 Supertone Inc.

```

*Including the license in a Python package’s [`setup.cfg`](https://github.com/supertone-inc/supertonic/blob/main/setup.cfg)*:

```ini
[metadata]
license = MIT
license_file = LICENSE

```

*Referencing the license in a README*:

```markdown

## License

Supertonic is released under the MIT License – see the [LICENSE file](https://github.com/supertone-inc/supertonic/blob/main/LICENSE) for details.

```

## Summary

- Supertonic is licensed under the **MIT License**, with full text available in the repository root `LICENSE` file.
- The license permits unrestricted use, modification, distribution, and sublicensing in proprietary applications.
- Attribution requires preserving the copyright notice and license text in all copies or substantial portions of the software.
- License declarations appear consistently across [`nodejs/package.json`](https://github.com/supertone-inc/supertonic/blob/main/nodejs/package.json), [`py/pyproject.toml`](https://github.com/supertone-inc/supertonic/blob/main/py/pyproject.toml), [`rust/Cargo.toml`](https://github.com/supertone-inc/supertonic/blob/main/rust/Cargo.toml), and [`java/pom.xml`](https://github.com/supertone-inc/supertonic/blob/main/java/pom.xml).

## Frequently Asked Questions

### Is Supertonic free for commercial use?

Yes, the MIT License explicitly permits commercial use without restriction. You may incorporate Supertonic into paid products, services, or internal tools without purchasing additional licenses or paying royalties to Supertone Inc.

### Do I need to open-source my code if I use Supertonic?

No, the MIT License does not impose copyleft requirements. You may use Supertonic in proprietary, closed-source applications provided you include the original copyright notice and MIT license text with your distribution.

### Where can I find the full license text for Supertonic?

The complete MIT license text resides in the `LICENSE` file at the root of the `supertone-inc/supertonic` repository. Language-specific bindings also reference this license in their respective configuration files, including [`nodejs/package.json`](https://github.com/supertone-inc/supertonic/blob/main/nodejs/package.json), [`py/pyproject.toml`](https://github.com/supertone-inc/supertonic/blob/main/py/pyproject.toml), [`rust/Cargo.toml`](https://github.com/supertone-inc/supertonic/blob/main/rust/Cargo.toml), and [`java/pom.xml`](https://github.com/supertone-inc/supertonic/blob/main/java/pom.xml).

### What copyright notice must I include when using Supertonic?

You must include the original copyright notice from the `LICENSE` file, which typically reads "Copyright (c) [year] Supertone Inc." along with the full permission notice and license text. This attribution must appear in all copies or substantial portions of the software.