PHPackages ioweb-gr/m1\_phpstan\_bridge - 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. [Testing & Quality](/categories/testing) 4. / 5. ioweb-gr/m1\_phpstan\_bridge ActiveLibrary[Testing & Quality](/categories/testing) ioweb-gr/m1\_phpstan\_bridge ============================ Generate PHPStan stubs from OpenMage PhpStorm meta files. 03PHP Since Apr 28Pushed 1mo agoCompare [ Source](https://github.com/ioweb-gr/m1_phpstan_bridge)[ Packagist](https://packagist.org/packages/ioweb-gr/m1_phpstan_bridge)[ RSS](/packages/ioweb-gr-m1-phpstan-bridge/feed)WikiDiscussions master Synced 1w ago READMEChangelogDependenciesVersions (1)Used By (0) M1 PHPStan Bridge ================= [](#m1-phpstan-bridge) Generate a lightweight PHPStan bridge for Magento 1 / OpenMage from n98-magerun PhpStorm metadata. The package does not bootstrap Magento and does not evaluate Magento config. It consumes already-generated `.phpstorm.meta.php` files and converts them into PHPStan map files, dynamic return type extensions, augmentation stubs, and a classmap autoloader. Requirements ------------ [](#requirements) - PHP 8.2+ - Composer - PHPStan in the target Magento project - n98-magerun metadata generated in the target Magento project The repository includes `mise.toml` entries for PHP 8.2 on Linux and Windows. Install ------- [](#install) ``` composer install ``` Prepare Magento Metadata ------------------------ [](#prepare-magento-metadata) Run this in the Magento project first: ``` n98-magerun dev:ide:phpstorm:meta ``` If metadata is missing, the generator fails with: ``` Unable to find .phpstorm.meta.php metadata. Run n98-magerun dev:ide:phpstorm:meta first. ``` Generate -------- [](#generate) ``` php bin/generate-stubs "/path/to/magento/root" --validate ``` The generator searches common metadata locations, including: ``` /path/to/magento/root/.phpstorm.meta.php ``` You can also pass metadata explicitly: ``` php bin/generate-stubs "/path/to/magento/root" --meta-path="/path/to/.phpstorm.meta.php" ``` Generated files are written under: ``` .m1_phpstan_bridge/ ``` PHPStan Usage ------------- [](#phpstan-usage) Include the generated config from your project PHPStan config: ``` includes: - .m1_phpstan_bridge/phpstan-magento.neon ``` The generator registers the generated PHPStan extension namespace in the target project `composer.json` under `autoload-dev`: ``` "M1PhpStanBridgeGenerated\\": ".m1_phpstan_bridge/src/" ``` Run `composer dump-autoload` after generation if you do not use `--validate`. Generated Files --------------- [](#generated-files) Core bridge files: ``` .m1_phpstan_bridge/phpstan-magento.neon .m1_phpstan_bridge/stubs/**/*.stub.php .m1_phpstan_bridge/autoload.php .m1_phpstan_bridge/classmap-autoload.php .m1_phpstan_bridge/src/PHPStan/*.php ``` Generated data and reports: ``` .m1_phpstan_bridge/generated/model-map.php .m1_phpstan_bridge/generated/singleton-map.php .m1_phpstan_bridge/generated/resource-model-map.php .m1_phpstan_bridge/generated/helper-map.php .m1_phpstan_bridge/generated/block-map.php .m1_phpstan_bridge/generated/class-map.php .m1_phpstan_bridge/generated/diagnostics.json .m1_phpstan_bridge/generated/classmap-report.md .m1_phpstan_bridge/generated/phpstan-smoke.php ``` Structural Stubs ---------------- [](#structural-stubs) Structural stubs are augmentation-only. Real Magento/OpenMage classes are loaded through PHPStan `scanFiles`, `scanDirectories`, and the generated classmap autoloader; they are not duplicated into stubs. Generated stubs are split per class under: ``` .m1_phpstan_bridge/stubs/ ``` Current generated augmentations cover methods where Magento's source signature is too weak for PHPStan, such as factory methods and selected `Varien_Object`data methods. Example paths: ``` .m1_phpstan_bridge/stubs/Mage.stub.php .m1_phpstan_bridge/stubs/Varien/Object.stub.php ``` The generator removes obsolete root-level stubs such as `magento-core.stub.php`when regenerating. `--validate` fails if any generated stub file exceeds 1MB and prints the class/namespace responsible; oversized stubs usually mean real classes are being duplicated instead of loaded through classmap or scan config. What It Supports ---------------- [](#what-it-supports) Dynamic return type extensions are generated for: - `Mage::getModel()` - `Mage::getSingleton()` - `Mage::getResourceModel()` - `Mage::helper()` - `Mage::getBlockSingleton()` - `Mage_Core_Model_Layout::createBlock()` Each extension reads the generated map file, inspects the first argument when it is a constant string, and returns `ObjectType($class)` when the alias is known. Unknown or dynamic aliases fall back gracefully. Classmap Discovery ------------------ [](#classmap-discovery) The generator scans Magento-style source locations: ``` app/code/core app/code/community app/code/local lib/Varien lib/Zend ``` Class discovery is token-based and only records declared symbols: - class declarations - interface declarations - trait declarations - enum declarations when supported by the PHP runtime It does not map referenced symbols from static calls, `::class`, `instanceof`, type hints, PHPDoc, setup variables, or other references. Setup/data/test/temp/vendor/node paths are excluded from classmap scanning. Files with executable top-level code before declarations are skipped for autoload safety and reported in `classmap-report.md`. `diagnostics.json` reports unresolved aliases when n98 metadata points to a class that is not present in the generated declared-symbol classmap. This usually means the metadata is stale, the module config maps an alias to a class that is not present in the checkout, or the real class has a different prefix than the alias metadata suggests. Validation ---------- [](#validation) `--validate` performs: - `composer dump-autoload` in the target Magento project - generated stub file size checks; any single stub over 1MB fails validation with the responsible class/namespace in the diagnostic - `php -l` on generated PHP files - expected core alias checks - a non-`dumpType` PHPStan smoke test: ``` vendor/bin/phpstan analyse .m1_phpstan_bridge/generated/phpstan-smoke.php -c .m1_phpstan_bridge/phpstan-magento.neon --memory-limit=1G ``` The smoke test exits `0` when factory/helper/block aliases infer the expected concrete types. Notes ----- [](#notes) - The old giant `mage.stub.php` conditional-return strategy is not used. - Structural stubs are augmentation-only and split per class. - No broad `ignoreErrors` rules are generated. - The bridge is intended to reduce Magento dynamic false positives while still allowing PHPStan to report real module issues. ### Health Score 20 — LowBetter than 13% of packages Maintenance60 Regular maintenance activity Popularity3 Limited adoption so far Community6 Small or concentrated contributor base Maturity11 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure 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. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/20220341?v=4)[IOWEB TECHNOLOGIES](/maintainers/ioweb-gr)[@ioweb-gr](https://github.com/ioweb-gr) --- Top Contributors [![ioweb-gr](https://avatars.githubusercontent.com/u/20220341?v=4)](https://github.com/ioweb-gr "ioweb-gr (12 commits)") ### Embed Badge ![Health badge](/badges/ioweb-gr-m1-phpstan-bridge/health.svg) ``` [![Health](https://phpackages.com/badges/ioweb-gr-m1-phpstan-bridge/health.svg)](https://phpackages.com/packages/ioweb-gr-m1-phpstan-bridge) ``` ### Alternatives [szepeviktor/phpstan-wordpress WordPress extensions for PHPStan 3309.4M1.2k](/packages/szepeviktor-phpstan-wordpress)[dms/phpunit-arraysubset-asserts This package provides ArraySubset and related asserts once deprecated in PHPUnit 8 14228.7M340](/packages/dms-phpunit-arraysubset-asserts)[jasonmccreary/laravel-test-assertions A set of helpful assertions when testing Laravel applications. 3524.1M38](/packages/jasonmccreary-laravel-test-assertions)[orchestra/workbench Workbench Companion for Laravel Packages Development 8219.1M67](/packages/orchestra-workbench)[soyuka/contexts Behatch contexts 282.2M21](/packages/soyuka-contexts)[roquie/laravel-dusk-select2 Select2.js support for the Laravel Dusk testing. 41356.2k5](/packages/roquie-laravel-dusk-select2) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)