# d3p1/module-home-popup > Home popup `composer require d3p1/module-home-popup` Canonical URL: https://packagento.com/d3p1/module-home-popup ## At a glance - **Vendor**: d3p1 (https://packagento.com/d3p1.md) - **Latest version**: v1.0.0 — released 2026-05-06 - **Pricing**: Free - **Package type**: Magento 2 module - **Status**: active, accepting new buyers ## Installation Packagento is licence-gated, so even free packages need a licence on a project before Composer can resolve them. 1. **Sign in or create an account** at https://packagento.com/customer/account/. 2. **Add the package to your account.** Open https://packagento.com/d3p1/module-home-popup and complete the free checkout. A licence is minted automatically. 3. **Create or pick a project, then activate the licence on it.** - Projects represent the Magento installs you deploy to. Manage them at https://packagento.com/projects/. - Activate the new licence on the project you'll deploy this package to. Activation is what generates the Composer credentials scoped to that project. 4. **Add the project credentials to your Magento codebase.** Grab the project's public + private key from https://packagento.com/projects/ (open the project, then its Credentials tab), and add them to `auth.json`: ```json { "http-basic": { "packagento.com": { "username": "ppk_live_...", "password": "psk_live_..." } } } ``` Add the Packagento Composer repository to `composer.json`: ```json { "repositories": [ { "type": "composer", "url": "https://packagento.com" } ] } ``` 5. **Install and apply.** ```bash composer require d3p1/module-home-popup:* bin/magento setup:upgrade bin/magento setup:di:compile bin/magento cache:flush ``` ## What it does Home popup ## README
## [LIBRARY PHP TEMPLATE] [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)](https://github.com/prettier/prettier) [![Release](https://github.com/d3p1/lib-php-template/actions/workflows/release.yml/badge.svg)](https://github.com/d3p1/lib-php-template/actions/workflows/release.yml) [![semantic-release: angular](https://img.shields.io/badge/semantic--release-angular-e10079?logo=semantic-release)](https://github.com/semantic-release/semantic-release)
### Introduction A template to build [PHP](https://www.php.net/) libraries. The goal of this template is to simplify the process of creating, maintaining, and publishing libraries. It provides a ready-to-use setup with sensible defaults, including an [automated release workflow triggered on every push to the repository](./.github/workflows/release.yml). ### Usage Using this library is straightforward: --- #### 1. Create a repository Click the **[Use this template](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)** button to create a new repository based on this template. --- #### 2. Update `composer.json` Edit the [`composer.json`](./composer.json) file to reflect your library’s metadata: - `name` – Your library name - `description` – Short and meaningful description - `authors` – Author information - `require` - Library dependencies - `autoload` - Autoload configuration --- #### 3. Install dependencies Execute the following commands: ```bash composer install ``` --- #### 4. Develop your library Start developing your library inside the [`src` folder](./src). Every commit must follow this [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format: ``` (): [] ``` > [!NOTE] > This is required by the [release workflow, which analyzes every commit to automatically generate the releases](./.github/workflows/release.yml). --- #### 5. Finalize documentation Update the [`README.md`](./README.md) to describe your library’s purpose and usage. > [!IMPORTANT] > Don’t forget to update the release badge URL at the top of this file if you keep it — it currently points to this repository. --- > [!NOTE] > To gain a deeper understanding of how to use this library and how it works under the hood, visit the [wiki page](https://github.com/d3p1/lib-php-template/wiki) _(in progress)_. > [!NOTE] > There is a [ticket](https://github.com/d3p1/lib-php-template/issues/2) to add testing tools to improve the library's validation workflow. ### Changelog Detailed changes for each release are documented in [`CHANGELOG.md`](./CHANGELOG.md). ### License This work is published under [MIT License](./LICENSE). ### Author Always happy to receive a greeting on: - [LinkedIn](https://www.linkedin.com/in/cristian-marcelo-de-picciotto/) - [Web](https://d3p1.dev/) ## Changelog #### Features * init [[#1](https://github.com/d3p1/magento2-home-popup/issues/1)] ([c31d84d](https://github.com/d3p1/magento2-home-popup/commit/c31d84db757b4e9b1e3a3fa99af000e7d36ed752)) ## 1.0.0 (2026-04-22) #### Features * add base composer definition [[#1](https://github.com/d3p1/lib-php-template/issues/1)] ([8f5e57d](https://github.com/d3p1/lib-php-template/commit/8f5e57d060055bca33fc82ee29a04b0a024b2848)) * init [[#1](https://github.com/d3p1/lib-php-template/issues/1)] ([b35bf70](https://github.com/d3p1/lib-php-template/commit/b35bf70817e6a830fa5baf6dba79f11eb0936271)) ## Recent Versions | Version | Released | |---|---| | v1.0.0 | 2026-05-06 | ## Dependencies ### Require | Package | Constraint | |---|---| | magento/framework | ~101.0\|\|~102.0\|\|~103.0 | | magento/module-cms | ~103.0\|\|~104.0 | | magento/module-theme | ~101.0 | | php | ^7.0.0\|\|^8.0.0 | ## Quality Latest release (v1.0.0) fails the Packagento QA pipeline. Verdicts below are per-cell (Magento line × PHP version) for the matrixed tools, and run-once for the static / security tiers. ### Compatibility Each Magento line is installed on its supported PHP versions, then the module is built (DI compile + static-content deploy). Cells show passed / failed / untested; staircase gaps render as `–`. | Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 | |---|---|---|---|---| | 2.4.7 | not tested | not tested | – | – | | 2.4.8 | – | not tested | Pass | – | | 2.4.9 | – | – | not tested | Pass | ### Code Quality Advisory checks against the module's source. Never affect the Compatibility verdict — 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. | Tool | Status | Findings | Summary | |---|---|---|---| | PHPCS | Fail | 11 | 4 errors, 7 warnings (ruleset: Magento2) — 5 auto-fixable with phpcbf | | PHPMD | Pass | 0 | | | Cpd | Pass | 0 | | | Composer validate | Info | 4 | valid; 4 advisory notes (composer validate --strict) | #### PHPStan Type-checks the module against a real Magento install. Re-runs per Magento + PHP version because resolvable symbols differ between releases. | Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 | |---|---|---|---|---| | 2.4.7 | Pass | Pass | – | – | | 2.4.8 | – | Pass | Pass | – | | 2.4.9 | – | – | Pass | Pass | ### Tests Unit and integration suites run per Magento + PHP cell. Test failures speak to the module's behaviour, not its compatibility with a line, so they're reported here separately. #### 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 Dependency-advisory audit (composer audit) plus a source malware scan. A malware detection fails the version outright. | Tool | Status | Findings | Summary | |---|---|---|---| | Composer audit | Pass | 0 | | | Malware scan | Pass | 0 | | ## Licence and pricing Free. A licence is still minted on checkout and bound to your project for Composer access — no payment step. Refundable within 14 days of first purchase via https://packagento.com/account/refunds/. ## Install via Claude Code or any MCP client The Packagento MCP server can run the licence + project + Composer steps above in one tool call: ``` purchase_and_install_packages( composer_names=["d3p1/module-home-popup"], project_id="proj_xxx" ) ``` This handles cart, checkout, licence minting, project activation, and writes auth.json credentials. Connect a client with `claude mcp add packagento https://mcp.packagento.com`. Full setup at https://packagento.com/docs/mcp-setup. ## Vendor d3p1 is a Magento 2 vendor on Packagento. See https://packagento.com/d3p1.md for their full catalogue.