PHPackages                             propeople/update\_project\_components\_statuses - 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. propeople/update\_project\_components\_statuses

ActiveLibrary[Utility & Helpers](/categories/utility)

propeople/update\_project\_components\_statuses
===============================================

Enable/revert the features from the profile "\*.info" file or file, that stored in "sites/default/components.info".

151

Since Jan 29Pushed 11y agoCompare

[ Source](https://github.com/BR0kEN-/update_project_components_statuses)[ Packagist](https://packagist.org/packages/propeople/update_project_components_statuses)[ RSS](/packages/propeople-update-project-components-statuses/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Update the Project Components statuses (Drush command)
======================================================

[](#update-the-project-components-statuses-drush-command)

Did you have a situation when your Drupal project contains a lot of features that need to be reverted after the regular code deployment? The `drush upcs`command is enabled/reverted the necessary modules/features.

To let the command know what should be checked, a special file in "sites/default" that named "components.info" should be created. Also, the contents of that file can be placed into an installation profile "\*.info" file and described previous step can be ommited.

Example of contents from "\*.info" file:

```
; Features
components[] = feature_name

; Modules
components[] = module_name

```

Usage
-----

[](#usage)

Enable or revert all modules or features if it necessary.

```
drush upcs

```

Installation
------------

[](#installation)

You can just execute the `drush dl update_project_components_statuses` and Drush download the package into your `~/.drush` folder.

Another way to install this command - is manually download the sources and place it into `~/.drush` folder by yourself.

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity41

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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/0e8b4c73b9ba0729e2c5b690cbdb63bfbe982130513b0c9d64c6c26e1d4d32ff?d=identicon)[BR0kEN-](/maintainers/BR0kEN-)

---

Top Contributors

[![BR0kEN-](https://avatars.githubusercontent.com/u/2760616?v=4)](https://github.com/BR0kEN- "BR0kEN- (5 commits)")

---

Tags

drushdrush-commands

### Embed Badge

![Health badge](/badges/propeople-update-project-components-statuses/health.svg)

```
[![Health](https://phpackages.com/badges/propeople-update-project-components-statuses/health.svg)](https://phpackages.com/packages/propeople-update-project-components-statuses)
```

PHPackages © 2026

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