# GeoLibre License: Which Open-Source License Does the GeoLibre Project Use?

> Discover the GeoLibre project license. GeoLibre uses the MIT License, a flexible open-source license for commercial and private use. Learn more.

- Repository: [Open Geospatial Solutions/GeoLibre](https://github.com/opengeos/GeoLibre)
- Tags: licensing
- Published: 2026-08-16

---

**The GeoLibre project is released under the MIT License**, a permissive open-source license that allows commercial use, modification, distribution, and private use with minimal restrictions.

GeoLibre is a geospatial data processing library maintained by the opengeos organization. Understanding its licensing terms is essential for developers integrating the library into commercial products, academic research, or derivative open-source projects. The MIT License is declared consistently across the repository's configuration files and the canonical license text resides in the root-level `LICENSE` file.

## Where the MIT License Is Declared in GeoLibre

The GeoLibre project follows standard open-source conventions by placing license information in multiple locations for discoverability.

### Root-Level LICENSE File

The authoritative license text lives at the repository root:

```

https://github.com/opengeos/GeoLibre/blob/main/LICENSE

```

This file contains the full MIT License text, including the copyright notice and permission grant. When redistributing GeoLibre or creating derivative works, this file must be included to comply with license terms.

### Python Package Configuration

The Python implementation explicitly declares the license in its build configuration. In [`python/pyproject.toml`](https://github.com/opengeos/GeoLibre/blob/main/python/pyproject.toml), the metadata includes:

```toml
license = "MIT"

```

This declaration ensures that package managers like **pip** and **PyPI** correctly index GeoLibre's licensing terms. Tools that audit dependencies for license compliance will automatically detect this field.

### JavaScript/TypeScript Package Manifests

GeoLibre's monorepo structure includes multiple npm workspaces, each with its own [`package.json`](https://github.com/opengeos/GeoLibre/blob/main/package.json). These files consistently specify the MIT License. For example, [`apps/geolibre-desktop/package.json`](https://github.com/opengeos/GeoLibre/blob/main/apps/geolibre-desktop/package.json) includes:

```json
{
  "license": "MIT"
}

```

This pattern repeats across workspace packages, ensuring uniform licensing regardless of which specific GeoLibre module you install via npm or yarn.

## How to Programmatically Read the GeoLibre License

While the license itself isn't executable code, you may need to display or validate license information in applications that depend on GeoLibre.

### Reading the License in Node.js

Use the `fs` module to load the license text from the repository structure:

```javascript
import { readFileSync } from 'fs';
import { join } from 'path';

const licensePath = join(import.meta.dirname, '..', '..', 'LICENSE');
const licenseText = readFileSync(licensePath, 'utf8');

console.log('GeoLibre License:\n', licenseText);

```

This approach works when GeoLibre is installed as a dependency where the `LICENSE` file is preserved in the package distribution.

### Reading the License in Python

Use `importlib.resources` to access bundled license files within the installed package:

```python
import importlib.resources as pkg_resources

license_text = pkg_resources.read_text('geolibre', 'LICENSE')
print('GeoLibre License:\n', license_text)

```

Note: This requires that the `LICENSE` file is included in the package's `MANIFEST.in` or [`pyproject.toml`](https://github.com/opengeos/GeoLibre/blob/main/pyproject.toml) `include` directives to be present in the installed distribution.

## What the MIT License Permits for GeoLibre Users

The MIT License grants four primary freedoms with minimal obligations:

1. **Commercial use** — You may use GeoLibre in proprietary, for-profit applications without paying royalties or licensing fees.

2. **Modification** — You can fork, modify, and improve GeoLibre's source code to suit your specific geospatial processing needs.

3. **Distribution** — You may distribute GeoLibre's original or modified versions as part of larger software packages.

4. **Private use** — You can use GeoLibre in internal tools without any disclosure requirements.

The sole requirement is preserving the copyright notice and permission notice in all copies or substantial portions of the software.

## Key Files Reference

| File Path | Purpose |
|-----------|---------|
| `LICENSE` | Contains the complete MIT License legal text |
| [`python/pyproject.toml`](https://github.com/opengeos/GeoLibre/blob/main/python/pyproject.toml) | Python package metadata with `license = "MIT"` |
| [`apps/geolibre-desktop/package.json`](https://github.com/opengeos/GeoLibre/blob/main/apps/geolibre-desktop/package.json) | Example npm workspace license declaration |
| [`package.json`](https://github.com/opengeos/GeoLibre/blob/main/package.json) (root) | Root monorepo license specification |

## Summary

- **GeoLibre uses the MIT License**, a permissive open-source license suitable for commercial and academic use.
- The license is declared in `LICENSE` at the repository root and echoed in [`python/pyproject.toml`](https://github.com/opengeos/GeoLibre/blob/main/python/pyproject.toml) and workspace [`package.json`](https://github.com/opengeos/GeoLibre/blob/main/package.json) files.
- The MIT License requires only that you preserve the copyright and permission notices when redistributing the code.
- You can programmatically read the license using standard file system APIs in Node.js or `importlib.resources` in Python.

## Frequently Asked Questions

### Is GeoLibre free to use in commercial applications?

Yes. The MIT License explicitly permits commercial use without restrictions. You can incorporate GeoLibre into proprietary products, SaaS platforms, or client deliverables without paying licensing fees or open-sourcing your own code. You must only include the original MIT License notice with any distribution of GeoLibre itself.

### Do I need to open-source my project if I use GeoLibre?

No. The MIT License does not impose copyleft requirements. Unlike GPL-licensed libraries, GeoLibre can be used in closed-source applications. Your project's source code remains yours to license independently. The only requirement is preserving GeoLibre's license notice in distributions that include the library.

### Where can I find the exact license text for GeoLibre?

The canonical license text resides in the repository root at `LICENSE`. For the Python package specifically, the license is also declared as metadata in [`python/pyproject.toml`](https://github.com/opengeos/GeoLibre/blob/main/python/pyproject.toml). Both sources confirm the MIT License. When installing via pip or npm, the license information is also available through package metadata queries (e.g., `pip show geolibre` or `npm info geolibre`).