PHPackages wp-forge/wp-plugin - 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 & Helpers](/categories/utility) 4. / 5. wp-forge/wp-plugin ActiveWordpress-plugin[Utility & Helpers](/categories/utility) wp-forge/wp-plugin ================== Create a new WordPress plugin via Composer 1.0.5(2y ago)1131GPL-2.0-or-laterPHPPHP >=7.4 Since Nov 3Pushed 2y ago1 watchersCompare [ Source](https://github.com/wp-forge/wp-plugin)[ Packagist](https://packagist.org/packages/wp-forge/wp-plugin)[ RSS](/packages/wp-forge-wp-plugin/feed)WikiDiscussions main Synced 1mo ago READMEChangelog (6)Dependencies (1)Versions (7)Used By (0) WordPress Plugin ================ [](#wordpress-plugin) A WordPress plugin scaffolding template that can be easily installed using Composer. Requirements ------------ [](#requirements) - [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - [Composer](https://getcomposer.org/doc/00-intro.md) - [Node](https://nodejs.org/) - [Docker](https://www.docker.com/) (optional) Installation ------------ [](#installation) Run this command in the terminal: ``` composer --remove-vcs create-project wp-forge/wp-plugin ``` **Be sure to append a directory name to the end of the command to customize the folder name that your project will be installed into!** The installation process will check your environment for the required PHP version and PHP extensions. If this presents a problem and you want to force install anyway, just add the `--ignore-platform-reqs` flag to the command. Notes ----- [](#notes) - The `.scripts` and `.templates` folders are used for scaffolding purposes only and won't exist in your end project. - We use the `@wordpress/env` package to provide a local development environment. This package requires Docker to be installed on your machine. If you don't want to use Docker, you can remove the `@wordpress/env` package from the `package.json` file and delete the `.wp-env.json` file. - We use the concept of a hooks folder. Rather than having a bunch of WordPress hooks scattered around your plugin, the `hooks` folder contains an `actions` and `filters` folder where each file name corresponds to the name of a hook (except with dashes in place of underscores). All items that belong in a particular hook are added to the appropriate file, making it easy to find, edit, and add hooks in a consistent way. - This repo has a `source` folder, where you can store any files that require a build step (e.g. scss and js). The `assets` folder is where you store the compiled files that will be used in your plugin. By default, we .gitignore the `assets/css` and `assets/js` folders. - Currently, this template does not implement any kind of build process. This is something that will be added in the future. - This repo creates an `.nvmrc` file. If you use [NVM](https://github.com/nvm-sh/nvm), you'll be able to run `nvm use`to automatically switch to the correct version of Node for this project. It will default to the version of Node that is running on your machine at the time of install. - This template creates GitHub Action workflows for your plugin. If you are publicly releasing your plugin on the WordPress.org plugin directory, you will need to add a `SVN_USERNAME` and `SVN_PASSWORD` environment variable to your GitHub repository settings. - If your plugin is to be publicly released, the `.wporg` folder is used to store the assets that will be uploaded to the WordPress.org plugin repository. Reminders --------- [](#reminders) Don't forget to: - Run `git remote add origin ` to add your remote repository - Add a `SVN_USERNAME` and `SVN_PASSWORD` environment variable to your GitHub repository settings (if your plugin is to be publicly released) - Push your code to GitHub by running `git push -u origin master` ### Health Score 23 — LowBetter than 27% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity8 Limited adoption so far Community8 Small or concentrated contributor base Maturity47 Maturing project, gaining track record 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. ### Release Activity Cadence Every ~0 days Total 6 Last Release 927d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/ae89dc177002c2f67341cde2d525e3f3c5b1d6aaaf07df15257a284f001c5551?d=identicon)[wpscholar](/maintainers/wpscholar) --- Top Contributors [![wpscholar](https://avatars.githubusercontent.com/u/890951?v=4)](https://github.com/wpscholar "wpscholar (28 commits)") ### Embed Badge ![Health badge](/badges/wp-forge-wp-plugin/health.svg) ``` [![Health](https://phpackages.com/badges/wp-forge-wp-plugin/health.svg)](https://phpackages.com/packages/wp-forge-wp-plugin) ``` ### Alternatives [umpirsky/transliterator Transliterator is a PHP library for text transliteration. 63174.9k1](/packages/umpirsky-transliterator)[wp-forge/wp-update-handler A WordPress package for updating custom plugins and themes based on an API response from a custom update server. 14135.8k](/packages/wp-forge-wp-update-handler) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)