Lacspace Free Licence

Lacspace Free Licence v1.0

Free for everyone. Free forever. Under our name.Use, modify, redistribute and sell — personal or commercial — at no cost. Just keep the notice.

Free & permissivePermissiveLicenseRef-LacspaceFree-1.0Released August 2026

Applies to the packages we publish openly on npm (the @lacspace public scope).

In plain language

What this licence actually means

The legal text is short and permissive. Here it is, in one breath.

Free for any use, including in closed-source commercial products.

You may modify, merge, redistribute, sublicense and sell copies.

The only condition: keep the copyright and this licence notice in copies.

No warranty is given, and Lacspace is not liable for how you use it.

It does not grant rights to the Lacspace name, logo or trademarks.

One licence for every language — npm now; Python, C and C++ next.

The matrix

Permissions, conditions & limitations

Every right you get, the one thing you must do, and what isn't covered.

Permissions

  • Commercial useUse the software in commercial products and services, at no cost.
  • ModificationChange the source however you need.
  • DistributionShare the original or your modified copies.
  • Sublicense & sellRelicense within your own product and sell copies.
  • Private useUse and modify privately with no obligation to publish.

Conditions

  • Keep the noticeInclude the copyright and licence notice in substantial copies.

Limitations

  • No warrantyThe software is provided “as is”, without warranty of any kind.
  • No liabilityThe authors are not liable for any claim or damages.
  • No trademark grantThe Lacspace name and marks are not licensed to you.
How to comply

You already do

Install a package and the LICENSE file ships inside it — the notice travels with the code in node_modules. There is nothing to sign and no attribution page to build. The only time you act is if you vendor or fork the source.

  1. Install any package. npm i @lacspace/<name> — the LICENSE file ships inside the package.
  2. It just works. You already comply: the notice travels inside node_modules with the code.
  3. If you vendor or fork. Keep the LICENSE file (or its notice) alongside substantial copies you redistribute.
package.json
{
  "name": "@lacspace/seo",
  "version": "1.6.2",
  "license": "SEE LICENSE IN LICENSE",
  "files": ["dist", "LICENSE", "README.md"]
}

// SPDX-style reference: LicenseRef-LacspaceFree-1.0
One licence, every language

Where it applies

The same licence covers our npm packages today and the registries we publish to next.

npm (JavaScript / TypeScript)livePyPI (Python)plannedC / C++ librariesplannedOther package registriesplanned
The whole thing

Full licence text

Verbatim and canonical. Copy it, or grab the raw text.

LICENSE
Lacspace Free Licence
Version 1.0, August 2026

Copyright (c) 2026 Lacspace

PREAMBLE

This software is published by Lacspace under the Lacspace Free Licence — a free,
permissive licence that lets you use this software for any purpose, including in
commercial products and services, at no cost. It grants the same freedoms as
common permissive open-source licences; the only condition is that this notice
travels with the software. The canonical, always-current text of this licence is
maintained at https://lacspace.com/licenses/lacspace-free-1.0

GRANT OF RIGHTS

Permission is hereby granted, free of charge, to any person or organisation
obtaining a copy of this software and its associated documentation and data files
(the "Software"), to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the conditions below. These rights are
granted for any purpose, personal or commercial, and are perpetual, worldwide,
non-exclusive, and royalty-free.

CONDITIONS

The above copyright notice, this permission notice, and the name of this licence
("Lacspace Free Licence") shall be included in all copies or substantial portions
of the Software.

TRADEMARKS

This licence does not grant permission to use the trade names, trademarks, service
marks, logos, or product names of Lacspace, except as required to reproduce the
notice above or to describe the origin of the Software in a truthful manner.

DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

---

The Lacspace Free Licence is a source-available, permissive licence and is not (as
of this version) an OSI-approved licence. In substance it grants the same freedoms
as the MIT Licence. Learn more at https://lacspace.com/licenses
FAQ

Common questions

Can I use Lacspace packages in a commercial or closed-source product?

Yes. The Lacspace Free Licence lets you use, modify and ship the software in personal and commercial products — including closed-source ones — at no cost. The only condition is that you keep the copyright and licence notice in substantial copies.

How is this different from MIT?

In the freedoms it grants, it is equivalent to MIT — the same rights to use, modify, distribute and sell. It is published under the Lacspace name so all our packages, across every language, carry one consistent licence, and it adds an explicit trademark clause. It is source-available and permissive, but not (as of v1.0) an OSI-approved licence.

What do I actually have to do to comply?

Keep the LICENSE file (or the notice it contains) with the software when you redistribute substantial portions of it. That is the whole obligation.

Does it grant any rights to the Lacspace brand?

No. You may not use the Lacspace name, logo or trademarks to promote your product, beyond reproducing the notice and truthfully describing the origin of the code.

Will Python, C and C++ packages use this same licence?

Yes. The licence is written to be language-agnostic. As Lacspace publishes packages to PyPI and other registries, they will ship under the same Lacspace Free Licence.

What does npm show for the licence field?

npm's license field only accepts standard SPDX identifiers, so our packages declare “SEE LICENSE IN LICENSE” and ship the full text in the LICENSE file. The SPDX-style reference is LicenseRef-LacspaceFree-1.0.

Need a different tier?

This is the free tier

The Lacspace Free Licence covers the packages we publish openly. Commercial, client and private tiers — for products, bespoke work and company-internal code — live in the full Licence Centre on lacspace.com.