PHPackages                             dg/composer-frontline - 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. dg/composer-frontline

ActiveComposer-plugin[Utility & Helpers](/categories/utility)

dg/composer-frontline
=====================

Composer Frontline: updates all the version constraints in the composer.json file to latest version

v0.2(5y ago)288.4k↓50%2[1 issues](https://github.com/dg/composer-frontline/issues)1BSD-3-ClausePHPPHP >=7.1

Since Oct 31Pushed 5y ago1 watchersCompare

[ Source](https://github.com/dg/composer-frontline)[ Packagist](https://packagist.org/packages/dg/composer-frontline)[ RSS](/packages/dg-composer-frontline/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (5)Versions (3)Used By (1)

Composer Frontline
==================

[](#composer-frontline)

[![Downloads this Month](https://camo.githubusercontent.com/971224d379c2a54d99ef33009997ccb8df9192357cdc9a663d78f3ec7238126a/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f646d2f64672f636f6d706f7365722d66726f6e746c696e652e737667)](https://packagist.org/packages/dg/composer-frontline)

**Updates all the version constraints of dependencies in the composer.json file to their latest version.**

How do you update outdated dependencies?
----------------------------------------

[](#how-do-you-update-outdated-dependencies)

When you install a package using `composer require vendor/package`, a entry for example `"vendor/package": "^1.4"` is added to the composer.json file. It means that Composer can update to patch and minor releases: 1.4.1, 1.5.0 and so on. But not to major version, which means, in this example, 2.0 and higher.

To discover new releases of the packages, you run `composer outdated`. Some of those updates can be major releases. Running `composer update` won’t update the version of those.

To update to a new major versions, use this tool Composer Frontline.

Usage
-----

[](#usage)

Install it:

```
composer global require dg/composer-frontline
```

then run it:

```
composer frontline
```

it will print something like:

```
vendor/package      ^1.4  →  ^2.0
nette/mail          ^1.0  →  ^3.1
latte/latte         ^1.6  →  ^2.8

```

This will upgrade all the version hints in the composer.json file, in `require` and `require-dev` sections. It only modifies composer.json file. So run `composer update` to update your packages.

You can also update only specific packages using names and wildcards:

```
composer frontline  nette/*
composer frontline  doctrine/* symfony/console
```

Make sure your composer.json file is in version control and all changes have been committed. This will overwrite your composer.json file.

###  Health Score

29

—

LowBetter than 59% of packages

Maintenance19

Infrequent updates — may be unmaintained

Popularity34

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity40

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 85.7% 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 ~1 days

Total

2

Last Release

2025d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/17f266513a3ca97500ec3d85d562b9279c7a6346358fe2b8d90390ece717a027?d=identicon)[david@grudl.com](/maintainers/david@grudl.com)

---

Top Contributors

[![dg](https://avatars.githubusercontent.com/u/194960?v=4)](https://github.com/dg "dg (6 commits)")[![matej21](https://avatars.githubusercontent.com/u/1276059?v=4)](https://github.com/matej21 "matej21 (1 commits)")

---

Tags

composerupdatecomposer

###  Code Quality

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/dg-composer-frontline/health.svg)

```
[![Health](https://phpackages.com/badges/dg-composer-frontline/health.svg)](https://phpackages.com/packages/dg-composer-frontline)
```

###  Alternatives

[ergebnis/composer-normalize

Provides a composer plugin for normalizing composer.json.

1.1k37.3M2.1k](/packages/ergebnis-composer-normalize)[bamarni/composer-bin-plugin

No conflicts for your bin dependencies

52722.0M859](/packages/bamarni-composer-bin-plugin)[pyrech/composer-changelogs

Display changelogs after each composer update

5904.0M25](/packages/pyrech-composer-changelogs)[helhum/dotenv-connector

Makes it possible to set environment variables for composer projects.

1594.6M34](/packages/helhum-dotenv-connector)[mnsami/composer-custom-directory-installer

A composer plugin, to help install packages of different types in custom paths.

1395.0M52](/packages/mnsami-composer-custom-directory-installer)[ffraenz/private-composer-installer

A composer install helper for private packages

2331.7M5](/packages/ffraenz-private-composer-installer)

PHPackages © 2026

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