PHPackages                             algolia/magento2-tools - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. algolia/magento2-tools

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

algolia/magento2-tools
======================

Tools for magento 2 developers

v0.4.1(3mo ago)72.3k[2 PRs](https://github.com/algolia/magento2-tools/pulls)MITShell

Since Sep 30Pushed 1mo ago47 watchersCompare

[ Source](https://github.com/algolia/magento2-tools)[ Packagist](https://packagist.org/packages/algolia/magento2-tools)[ RSS](/packages/algolia-magento2-tools/feed)WikiDiscussions master Synced 2d ago

READMEChangelog (10)Dependencies (9)Versions (30)Used By (0)

 [ ![](https://raw.githubusercontent.com/algolia/algoliasearch-client-common/master/readme-banner.png) ](https://www.algolia.com)

#### The perfect starting point to analyse the PHP quality of our Algolia Magento 2 extension

[](#the-perfect-starting-point-to-analyse-the-php-quality-of-our-algolia-magento-2-extension)

💡 Getting Started
-----------------

[](#-getting-started)

First, install globally the `magento2-tools`:

```
composer global require algolia/magento2-tools
```

Make sure to place Composer's system-wide vendor bin directory in your `$PATH`so the `magento2-tool` executable can be located by your system.

Finally, you can launch the quality tools with:

```
{command} path/to/magento/extension [vendor/bin/path/]
```

The second argument is optional. If omitted, the scripts will attempt to auto-resolve the vendor bin directory by checking for a local `vendor/bin/` install (e.g. after running `composer install` in the package directory) and then falling back to the global Composer vendor bin. If neither is found, the tools are expected to be on your `$PATH`.

Here is the list of available commands:

- **`magento2-lint`**: Runs the linter and fixes the found issues - configuration file under `algoliasearch-magento-2/.php-cs-fixer.php`.
- **`magento2-analyse`**: Runs PHPStan static analysis. Uses `phpstan.neon` or `phpstan.neon.dist` from the extension directory if present; otherwise runs at level 1 with sensible defaults.
- **`magento2-php-compatibility`**: Checks if your code is compatible across all PHP versions supported by Magento.
- **`magento2-test`**: Runs all previous commands in `--dry-run` / read-only mode (coding style, PHP compatibility, and PHPStan analysis).

Release process
---------------

[](#release-process)

- Clear your the local repository with: `git add . && git reset --hard`
- Make sure you are on the latest master branch: `git checkout master && git pull`

> Note: make sure that there is no breaking changes and you may use `git tag --list` to check the latest release

- Bump version in the file `bin/magento2-update`
- Commit the `bin/magento2-update` with the message: `git commit -m "chore: bumps version to vX.X.X"`
- `git push`
- `git tag vX.X.X`
- `git push --tags`
- Create a new release with the name `vX.X.X` under .

> Developers will get the new version via the `auto-update` mechanism of this tool.

📄 License
---------

[](#-license)

magento2-tools is an open-sourced software licensed under the [MIT license](LICENSE).

###  Health Score

49

—

FairBetter than 94% of packages

Maintenance86

Actively maintained with recent releases

Popularity23

Limited adoption so far

Community18

Small or concentrated contributor base

Maturity59

Maturing project, gaining track record

 Bus Factor2

2 contributors hold 50%+ of commits

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~113 days

Recently: every ~358 days

Total

22

Last Release

92d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/86cfef5c1f5195df1a9db17a5f8ecb34455e1f0133a725de9acf7f2fb26ac6a1?d=identicon)[nunomaduro](/maintainers/nunomaduro)

---

Top Contributors

[![nunomaduro](https://avatars.githubusercontent.com/u/5457236?v=4)](https://github.com/nunomaduro "nunomaduro (30 commits)")[![cammonro](https://avatars.githubusercontent.com/u/986313?v=4)](https://github.com/cammonro "cammonro (19 commits)")[![rakesh-algolia](https://avatars.githubusercontent.com/u/101420377?v=4)](https://github.com/rakesh-algolia "rakesh-algolia (8 commits)")[![ratikant-singh](https://avatars.githubusercontent.com/u/101382014?v=4)](https://github.com/ratikant-singh "ratikant-singh (6 commits)")[![bsuravech](https://avatars.githubusercontent.com/u/7048136?v=4)](https://github.com/bsuravech "bsuravech (4 commits)")[![mohitalgolia](https://avatars.githubusercontent.com/u/101385480?v=4)](https://github.com/mohitalgolia "mohitalgolia (2 commits)")

---

Tags

phpmagentotools

### Embed Badge

![Health badge](/badges/algolia-magento2-tools/health.svg)

```
[![Health](https://phpackages.com/badges/algolia-magento2-tools/health.svg)](https://phpackages.com/packages/algolia-magento2-tools)
```

###  Alternatives

[wp-cli/wp-cli-tests

WP-CLI testing framework

423.0M130](/packages/wp-cli-wp-cli-tests)[drupal/core-dev

require-dev dependencies from drupal/drupal; use in addition to drupal/core-recommended to run tests from drupal/core.

2022.0M322](/packages/drupal-core-dev)[shopsys/coding-standards

Coding standards definition compatible with PSR-2

20276.8k20](/packages/shopsys-coding-standards)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
