Skip to content

GeoLeaf Notice and License Attribution ​

License ​

GeoLeaf Core is released under the MIT License.

© 2026 Mattieu Pottier
Released under the MIT License
https://geoleaf.dev

See the LICENSE file for the complete license text.


Core vs Modules ​

GeoLeaf Core (Open Source) ​

GeoLeaf Core is an open-source JavaScript mapping library. It includes:

  • Framework bootstrap - Application initialization and configuration
  • Core mapping - MapLibre GL JS wrapper and map management
  • Configuration system - Configuration loading and validation
  • Logging and errors - Unified logging and error handling
  • UI components - Base UI system, controls, panels
  • Security - XSS protection and input sanitization
  • Utilities - Helper functions and utility library

Perpetual Status: The GeoLeaf Core library is and will remain permanently open-source under the MIT License.

Optional Plugins ​

GeoLeaf offers optional plugins that extend Core functionality — offline cache and Service Worker, feature editing (geometry and attributes), COG rendering, printing, measuring, table views, file import, geocoding, real-time layers and more.

Every plugin is released under the MIT License, under the @geoleaf-plugins/* scope. The whole client-side library is MIT: install it, use it, ship it.

To find out which plugins are on the public registry, and at which version, run npm view <package> version. That is the only authoritative answer, and it is why no such list is reproduced here.

Plugins:

  • Are optional — Core works fully without them
  • Are independently versioned — each ships its own LICENSE, all MIT
  • Do not affect the MIT License of GeoLeaf Core

packages/core/ never references a plugin package. That boundary is an architectural one — it keeps the Core standalone and tree-shakeable — not a licence boundary.


Dependencies ​

GeoLeaf needs MapLibre GL JS (https://maplibre.org, BSD 3-Clause License), a peer dependency that the host application installs: it is not bundled in any GeoLeaf package.

The third-party code a GeoLeaf package does bundle is listed, with its license texts, in the THIRD_PARTY_LICENSES.txt file at the root of that package's npm tarball. The file is generated from the package's own built bundle, so it names what the bundle actually carries — not what its package.json declares — and it copies the license comments of the bundled source files, and, for a dependency published already built, of the original sources its own source map carries: that is where the notices of code a package vendors from others are kept.


Attribution and Acknowledgments ​

GeoLeaf thanks the following communities and projects:

  • MapLibre GL JS - Core mapping engine (WebGL)
  • OpenStreetMap - Mapping data and community
  • JavaScript mapping community - Design patterns and best practices

Contributing ​

When contributing to GeoLeaf, please ensure all new code includes the appropriate license header. See CONTRIBUTING.md for details.


Questions ​

For questions about licensing, see CONTRIBUTING.md or visit https://geoleaf.dev.

Released under the MIT License.