PHPackages                             enygma/composerclean - 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. [DevOps &amp; Deployment](/categories/devops)
4. /
5. enygma/composerclean

ActiveLibrary[DevOps &amp; Deployment](/categories/devops)

enygma/composerclean
====================

An additional command for Composer that removes configured files/directory

0.1(10y ago)181.8kMITPHPPHP &gt;=5.3.1

Since May 23Pushed 8y ago2 watchersCompare

[ Source](https://github.com/enygma/composerclean)[ Packagist](https://packagist.org/packages/enygma/composerclean)[ Docs](https://github.com/enygma/composerclean.git)[ RSS](/packages/enygma-composerclean/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (2)Used By (0)

"Clean" command for Composer
============================

[](#clean-command-for-composer)

With Composer being used often to build a package to deploy, it makes sense that there should be functionality to strip out certain things (like README or a `tests/` directory) that don't need to be deployed. With this addition you'll be given a command to "clean" the packages in your repositories and make it ready for deploy.

Usage
-----

[](#usage)

To use the package, you'll need two things. First, on your application you need to make the "clean" command available. First, install the latest version of the `ComposerClean` package:

```
composer require enygma/composerclean

```

Then you update your `composer.json` file to make it a command:

```
{
	"scripts": {
		"clean": "ComposerClean\\Clean::exec"
	}
}

```

Then you can fire off the cleaning process with a call to:

```
composer.phar clean

```

This will go through your installed repositories and remove the items marked in the project's "clean" list. To define this list in your own project, you put the list of directories or files in the `composer.json` configuration in the `extras` section:

```
{
	"extras": {
		"clean": [
			"tests/",
			"README.md",
			"LICENSE"
		]
	}
}

```

The command will do its best to remove the files and directories (recursing down) you've specified. The paths start from the root of the project so `tests/` would relate to something like `vendor/enygma/composerclean/tests` and everything under it.

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity23

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 80% 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

Unknown

Total

1

Last Release

4013d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/e3e9061cdcb718c070419cadac5c58261580bbb384d0c5db21e53501121f08a7?d=identicon)[enygma](/maintainers/enygma)

---

Top Contributors

[![enygma](https://avatars.githubusercontent.com/u/66796?v=4)](https://github.com/enygma "enygma (4 commits)")[![ccornutt](https://avatars.githubusercontent.com/u/16823013?v=4)](https://github.com/ccornutt "ccornutt (1 commits)")

---

Tags

composercleandeploy

### Embed Badge

![Health badge](/badges/enygma-composerclean/health.svg)

```
[![Health](https://phpackages.com/badges/enygma-composerclean/health.svg)](https://phpackages.com/packages/enygma-composerclean)
```

###  Alternatives

[banago/phploy

PHPloy - Incremental Git (S)FTP deployment tool that supports submodules, multiple servers and rollbacks.

1.4k47.2k](/packages/banago-phploy)[easycorp/easy-deploy-bundle

The easiest way to deploy Symfony applications

468310.2k](/packages/easycorp-easy-deploy-bundle)[jalogut/magento2-deployer-plus

Magento 2 deployment tool based on deployer.org

201415.5k](/packages/jalogut-magento2-deployer-plus)[hpatoio/deploy-bundle

Easy deploy via rsync. Porting of Symfony 1 project:deploy command.

3696.6k1](/packages/hpatoio-deploy-bundle)[ngmy/webloyer

Webloyer is a Web UI for managing Deployer deployments

2181.1k](/packages/ngmy-webloyer)[norsys/rothenberg

Tool which allow a developper to create or maintain a Symfony application or a Symfony bundle very easily and without install something on his workstation

2410.6k3](/packages/norsys-rothenberg)

PHPackages © 2026

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