Collider brings modern package management to Meson's native wrap ecosystem.
Rather than replacing Meson's dependency model, Collider extends it: automatic dependency resolution, lockfiles, and a streamlined day-to-day workflow, fully compatible with wraps and WrapDB.
It also lets teams run private WrapDB-compatible package repositories and publish to them, so you can build your own package ecosystem on the same infrastructure Meson already understands.
Documentation: collider.ee
Features
- Automatic dependency resolution for Meson wrap projects.
- Publishable wrap repositories.
- Host your own WrapDB-compatible package repository.
- Lockfiles for reproducible builds.
- Offline dependency cache.
- Compatible with WrapDB.
Why Collider?
Meson provides WrapDB and subprojects, but dependency management across multiple repositories can become difficult:
- Wrap files must be maintained manually.
- Offline builds require prefetching sources.
- Publishing reusable wraps is cumbersome.
Collider adds a lightweight package workflow on top of Meson's wrap system:
- Publishable wrap repositories.
- Self-hosted WrapDB-compatible registries.
- Reproducible dependency lockfiles.
- Offline dependency caching.
Requirements
- Python 3.10+
- Meson 1.8.5+ (and Ninja)
- See
pyproject.tomlfor Python dependency versions.
Installation
pip install collider-wraps
From source (development)
git clone git@github.com:MaxandreOgeret/collider.git
cd collider
uv venv
source .venv/bin/activate
uv sync
Quick start
From the root of a Meson project (next to meson.build):
collider init # create collider.json
collider repo add wrapdb wrap https://wrapdb.mesonbuild.com/v2/ # configure a repository
collider pkg add zlib # add a dependency
collider setup # configure the Meson build
collider lock # write collider.lock for reproducible installs
See the Quick Start guide for a full walkthrough.
Documentation
Full documentation lives at collider.ee:
- Getting started: install and first steps.
- User guide: managing packages, repositories, publishing, locking, offline mode, and serving.
- Configuration:
config.json,collider.json, andcollider.lock. - CLI reference: every command, flag, and exit code.
- Contributing: development setup and pull request checks.
License
Apache-2.0
Copyright 2026 MOG Robotics OÜ
Metadata
Release files for collider-wraps 1.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| collider_wraps-1.5.1.tar.gz | 101.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| collider_wraps-1.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 238.4 kB
Release files / collider_wraps-1.5.1.tar.gz
| Download URL | collider_wraps-1.5.1.tar.gz |
|---|---|
| Size | 101.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e66b4a58c18be0e8ad243549de566944a2ba148cddca94fc7082b32168e3791d
|
|
BLAKE2b-256 checksum How to use checksums |
d9f48077094d507834d12e6dddfd8fb5e6404c6e3576fe539c19fd250846d636
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logRelease files / collider_wraps-1.5.1-py3-none-any.whl
| Download URL | collider_wraps-1.5.1-py3-none-any.whl |
|---|---|
| Size | 137.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4765123cd7cb17da7b48ae9895a942db0c065fbeaaccdd3516649d867038e050
|
|
BLAKE2b-256 checksum How to use checksums |
ff997ea943e3cf9e2e4d19f8f128bcd2d784ca08ef8500831db01d0db03e2c71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency log