Quantum Computing Software Licenses: A Practical Guide to SDKs, Simulators, and Dependencies
licensingopen-sourcequantum-SDKssoftware-compliancecommercial-use

Quantum Computing Software Licenses: A Practical Guide to SDKs, Simulators, and Dependencies

QQubit Directory Editorial Team
2026-11-21
6 min read

A practical checklist for reviewing licenses, dependencies, hosted terms, and commercial-use risks in quantum SDKs and simulators.

Quantum software can be easy to install and surprisingly difficult to evaluate for commercial use. This guide provides a reusable license checklist for quantum SDKs, simulators, libraries, notebooks, example code, dependencies, and hosted quantum platforms.

Overview

Before adopting a quantum computing tool, determine more than whether it runs your circuit. You also need to know whether your team may use it internally, modify it, publish code built with it, redistribute it, or include it in a commercial product. The answer may differ between the core SDK, its dependencies, documentation, example notebooks, container images, plugins, and cloud service.

A license review should begin with the exact version and distribution channel you plan to use. Record the package name, version, source repository, package registry entry, and the date reviewed. Then locate the license file and identify its SPDX identifier, if one is provided. An SPDX identifier is a standardized short name for a software license, such as an identifier commonly used in package metadata. It makes automated review easier, but it does not replace reading the actual license text and notices.

Open-source availability is not the same as unrestricted use. Some licenses permit commercial use and modification with conditions such as preserving copyright notices, including the license text, documenting changes, or providing corresponding source under particular circumstances. Other projects may contain separate terms for hosted services, proprietary components, optional plugins, trained models, or example material. Treat each component as an item to verify rather than assuming that one repository-wide label covers everything.

This is a practical compliance workflow, not legal advice. If a planned distribution model, patent position, or customer contract creates material risk, ask qualified counsel to review the relevant license and your intended use.

Checklist by scenario

Using an SDK or simulator internally

  • Record the exact release, package source, repository URL, and license identifier.
  • Confirm that the license permits the intended internal activity, including development, testing, and research.
  • Review dependencies from the lockfile or manifest rather than checking only the top-level SDK.
  • Save the license text, notices, and review date with the project’s compliance records.
  • Check whether optional integrations, acceleration libraries, or provider plugins have separate terms.

Internal use is often simpler than redistribution, but it still deserves documentation. A simulator may pull in numerical libraries, compiler tools, runtime components, or visualization packages with different obligations. Reproducible experiments also depend on recording versions and environments; the reproducibility checklist for quantum experiments can complement the license review.

Modifying an open-source quantum SDK

  • Identify the license governing the files you plan to change, not just the repository’s landing-page summary.
  • Determine whether modification notices, copyright preservation, or source-availability obligations apply.
  • Keep a clear record of upstream version, local changes, patches, and contributors.
  • Check patent language and any conditions that could affect downstream use.
  • Decide whether your team will contribute changes upstream, maintain a private fork, or distribute a modified build.

Separate your modifications from third-party code where practical. This makes future upgrades, attribution, and release preparation easier. It also helps reviewers understand which obligations belong to the original project and which relate to your own additions.

Publishing research code, tutorials, or notebooks

  • Review the license for the code, documentation, notebook cells, datasets, and copied snippets separately.
  • Preserve required copyright and attribution notices.
  • Check whether examples supplied by an SDK have a license different from the SDK itself.
  • List dependencies and their versions so readers can reproduce the environment.
  • State the license for your original work clearly, without implying that you can relicense third-party material.

A notebook can combine original code, provider-specific examples, pasted documentation, circuit diagrams, and data. A single license statement at the top may not cover all of those materials. For research workflows, pair the license record with a dependency manifest and a citation record. The quantum research resources directory is useful when tracing papers, code repositories, and related research assets.

Distributing a commercial application or product

  • Generate a complete software bill of materials or equivalent dependency inventory.
  • Classify direct and transitive dependencies by license and distribution obligation.
  • Prepare the required notices, attribution files, and license texts before release.
  • Confirm whether static linking, bundling, containers, installers, or source distribution change the obligations.
  • Review patent provisions, warranties, export or procurement requirements, and customer-facing terms with the appropriate specialists.
  • Document exclusions: proprietary components, provider APIs, hosted services, and code that is not shipped with the product.

Commercial use of quantum software often involves a stack rather than a single tool: an SDK, a simulator, a transpiler, a cloud connector, an authentication client, and infrastructure libraries. Keep the software license review separate from the provider contract review. A permissive SDK license does not automatically grant rights to use a provider’s hosted API, data, branding, quota, or service output under any circumstances.

What to double-check

Use this compact record for every important quantum software component:

Review itemWhat to record
IdentityPackage, repository, version, commit or release tag, and distribution channel
LicenseSPDX identifier, full license text, copyright holder, and any exceptions
RightsInternal use, modification, redistribution, commercial use, and sublicensing position
ConditionsNotices, attribution, change disclosure, source availability, and documentation requirements
PatentsAny express patent grant, termination clause, or uncertainty requiring escalation
DependenciesDirect and transitive packages, native libraries, plugins, images, and build tools
Non-code contentExamples, notebooks, documentation, figures, datasets, and model artifacts
Hosted termsAPI, cloud platform, account, acceptable-use, data, output, and service-specific terms

Check the repository’s license file, package metadata, dependency manifest, release notes, and provider terms together. A version upgrade can change a dependency tree or distribution model even when your own source code is unchanged. If a project contains a license exception, dual-license notice, contributor agreement reference, or “non-commercial” example folder, flag it for closer review instead of reducing it to a generic label.

Common mistakes

  • Assuming public code is free of conditions. Public access does not remove attribution, notice, or redistribution requirements.
  • Checking only the top-level repository. Transitive dependencies and bundled assets can introduce separate obligations.
  • Confusing an SDK license with a cloud contract. Local libraries and hosted quantum services are governed by different documents.
  • Ignoring example code. Tutorials and notebooks may have separate copyright owners or terms.
  • Reviewing a project without pinning a version. A current repository branch may not describe the release in production.
  • Promising more than the license permits. Do not relicense third-party files or offer warranties on their behalf.
  • Failing to preserve the record. Without the reviewed version, source, and date, a later audit may be unable to reproduce the decision.

License questions can also affect tool selection. When comparing simulators or testing frameworks, include compliance requirements alongside performance, hardware compatibility, and workflow fit. For related evaluation criteria, see the guide to quantum circuit testing tools and CI workflows.

When to revisit

Revisit a license record before each seasonal planning or procurement cycle, and whenever workflows or tools change. At minimum, review it when you upgrade a major SDK, replace a simulator, add a provider integration, introduce a plugin, publish a notebook, build a container, or move from an internal prototype to customer delivery.

A practical maintenance rhythm is to scan important repositories and provider terms every six months, then perform a targeted review whenever a release changes its package structure or distribution model. Do not wait for a product launch to discover missing notices. Add license checks to dependency updates, release gates, and research-publication workflows.

Before acting, complete these final steps:

  1. Pin the exact versions and record the source locations.
  2. Export the dependency inventory and identify non-code assets.
  3. Collect license texts, notices, exceptions, and provider terms.
  4. Map each obligation to an owner and release task.
  5. Escalate ambiguous commercial, patent, or redistribution questions.
  6. Save the decision and set the next review trigger.

This process keeps quantum software adoption practical without treating licensing as an afterthought. Use the same record when evaluating a new quantum software platform, preparing a reproducible experiment, or comparing tools in a quantum computing directory.

Related Topics

#licensing#open-source#quantum-SDKs#software-compliance#commercial-use
Q

Qubit Directory Editorial Team

Editorial Team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.