Skip to content

License

SCIMAP Pro is not open source. It is distributed under the Scimappro Academic License 1.0 (LicenseRef-Scimappro-Academic-1.0), a source-available license that is free for noncommercial use and requires a paid license for commercial use.

Read this page before you build SCIMAP Pro into anything. The full text is what governs; the summary here is for orientation only.

The short version

You may

  • Use it for academic research, teaching, classroom work, and personal study.
  • Use it inside a nonprofit institute, public research organisation, charity, or government body — including one funded by industry, as long as the use is not commercial.
  • Redistribute verbatim, unmodified copies, keeping the license and notices.
  • Patch your own copy locally to fix a bug or a compatibility problem.
  • Own, publish, and sell everything you produce with it — figures, tables, annotations, models, results.
  • Own, publish, and sell code you write against the public API — scripts, notebooks, pipelines, and libraries that import scimappro or call its CLIs.

You may not

  • Publish, share, host, or sell a modified copy or fork — including public forks of the repository, patched builds, patched container images, or a modified version offered as a hosted service.
  • Use it for commercial purposes without a separate paid license. That covers use by a for-profit entity in its operations, fee-for-service contract research, paid services to third parties, and developing or supporting a product that is sold.
  • Charge a fee for the software itself.
  • Use the Nirmal Lab's names, marks, or the name "scimappro" beyond the descriptive use the notices require.

There is no patent grant, and no warranty. SCIMAP Pro is a research tool: it is not a medical device and is not validated or approved for clinical diagnosis, treatment, or any use involving patient care.

Your work is yours

This is the part people most often get wrong about source-available licenses, so it is worth stating plainly. Section 4 of the license says:

You own your Output. This License places no restriction on it […] you may publish, share, and commercialize the results of your analyses freely.

and

You may write, use, distribute, sell, and license Downstream Works without restriction under this License […] importing, calling, subclassing, wrapping, or invoking the command-line interfaces of the Software does not by itself make your Downstream Work a derivative work.

So a commercial pipeline that imports scimappro is fine to write, own, and sell — but running scimappro for a commercial purpose still needs a commercial license under Section 5, and any copy of scimappro you ship alongside your work must be verbatim.

Commercial licensing

For a commercial license, contact Ajit Johnson Nirmal ajitjohnson.n@gmail.com.

Contributing patches

Modifications you make stay inside your own organisation. You are encouraged — though not required — to send them upstream instead, where they can be released to everyone. See Contribute.

Third-party components

scimappro's dependencies are authored by other people and remain governed entirely by their own licenses. Nothing in the Scimappro Academic License restricts your rights in them, and where the two conflict for a given component, that component's license controls.

How this differs from SCIMAP

The community edition, SCIMAP, is MIT-licensed and stays that way. SCIMAP Pro is a separate package under separate terms; installing one does not change the license of the other.