vianetz / module-core
vianetz/module-core
The vianetz Magento core library that provides some utility methods for all our Magento extensions.
Vianetz Core Extension
Facts
- Version: 1.0.2
- Extension Key:
vianetz/module-core
Description
This extension provides basic functions for all vianetz Magento extensions.
Requirements
- PHP >= 5.3.6
Frequently Asked Questions
Please find the Frequently Asked Questions on our website vianetz.com/en/faq.
Support
If you have any issues or suggestions with this extension, please do not hesitate to
contact me at vianetz.com/en/contacts or [email protected].
Developer
Christoph Massmann
www.vianetz.com
@vianetz
Licence
GNU General Public License v3.0 (see also LICENSE file)
Copyright
(c) since 2008 vianetz
This Magento Extension uses Semantic Versioning - please find more information at semver.org.
Change Log
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog
and this project adheres to Semantic Versioning.
[1.0.2] - 2022-08-24
Added
- PHP 8 compatibility
[1.0.1] - 2019-11-04
Fixed
- Removed no longer allowed HTML tags in tab label in configuration
[1.0.0] - 2017-05-06
Added
- Initial version of the extension
Requires 2
| Package | Constraint |
|---|---|
| php | ^5.6|^7|^8 |
| magento/framework | * |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.