mibare

Mise Backend Resolver: recommends which mise backend to install a GitHub repository with

Table of Contents

• Installation
• Usage
• Support
• Motivation
• Features
• Author
• Analysis
• Contributing
• Development
• Releasing
• Credits
• License
• Changelog

Installation

mibare is a standalone end-user tool whose primary command is mibare. Install it into an isolated environment:

uv tool install mibare

Or run it without installing with uvx mibare. See the installation docs for pipx and from-source options.

Install with Homebrew (macOS/Linux):

brew install hasansezertasan/tap/mibare

Install with Scoop (Windows):

scoop bucket add hasansezertasan https://github.com/hasansezertasan/scoop-bucket
scoop install hasansezertasan/mibare

Verify the installation

The package root is importable after installation:

>>> from mibare import __doc__
>>> isinstance(__doc__, str)
True

Usage

CLI

mibare BurntSushi/ripgrep
mibare https://github.com/BurntSushi/ripgrep
mibare --help

The registry's backends for the repository are printed in registry order, the first marked as the recommendation. Exit code 0 means a recommendation was found, 1 that no backend was found, and 2 an error (input that is not a GitHub repository, or a missing or too-old mise; 2026.10.13 or newer is required).

Support ❤️

If you have any questions or need help, feel free to open an issue on the GitHub repository.

Motivation

A mise user who finds a tool on GitHub has no way to learn which mise backend to install it with. mise use accepts owner/repo but does not say which backend it chose, and its interactive selector only lists tools already in the mise registry. mibare takes a GitHub repository and recommends a backend (aqua:, github:, pypi:, cargo:, npm: or go:), ranked by mise's documented tier ladder, with legacy backends flagged. Terms follow the glossary; design decisions are in docs/adr/.

Features

• Library core: an importable package holding the resolution logic.
• CLI: a thin Typer wrapper around the library, run as mibare.

Author 🫅

This project is maintained by Hasan Sezer Taşan, It's me 👋

Analysis

• Snyk Python Package Health Analysis
• Libraries.io - PyPI
• Safety DB
• PePy Download Stats
• PyPI Download Stats
• Pip Trends Download Stats
• PyPI Map Dependency Graph

Contributing ❤️

Any contributions are welcome! Please follow the Contributing Guidelines to contribute to this project.

Development 🧰

See the Contributing Guidelines for local setup, the common development tasks (exposed via mise), building and previewing the documentation, and the VS Code debugging configurations.

Releasing

Versioning and releases are automated with release-please, driven by Conventional Commit PR titles squash-merged into main. release-please maintains a release PR that bumps the version and CHANGELOG.md; merging it tags the release and publishes to PyPI. See the Contributing Guidelines for the commit conventions, and the Repository setup guide for one-time configuration and optional post-launch integrations such as a social preview, downstream packaging, and Repology.

Pause merges that change .github/workflows/, including Renovate action-pin updates, from merging a release PR until the entire Release run finishes. Workflow differences between the release commit and current main can block tag or release creation with a 403 when using GITHUB_TOKEN. See Release recovery for prevention and recovery steps.

For adopting this project's tooling into an existing package, or reconciling a template update with existing project behavior, see the Template updates and Adopting into an existing project sections of REPOSITORY_SETUP.rst. They cover the baseline, workflow and required-check overlap, custom tooling and documentation, and ask for a decision before consequential cleanup. Work through the repository settings and release steps in the same file.

Credits

This package was created with Copier and the hasansezertasan/copier-pyproject project template.

License 📜

This project is licensed under the MIT License.

Changelog 📝

For a detailed list of changes, please refer to the CHANGELOG.