News Feed

News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Nils Adermann:
Composer Replace, Conflict & Forks Explained
February 19, 2014 @ 12:56:41

Nils Adermann has a new post looking at a problem with Composer where it will install a fork of a project rather than the actual project repository. He points out that it is not a security vulnerability in Composer itself, and is usually cause by using the configuration incorrectly.

Recently there has been an increase of cases in which Composer installs a fork of a package instead of the package the user expects. Most frequently these are forks of packages using a "replace" statement in their composer.json. These forks are usually meant for private use only but are still published on Packagist.

The issue stems from the use of "replace" and the publishing of those forked repositories in the Packagist service. "Replace" is meant to define a fork that is still compatible with the original project. The way that Composer handles finding the correct package to install can cause a conflict and the wrong package could end up "winning".

0 comments voice your opinion now!
composer replace fork repository dependency install


blog comments powered by Disqus

Similar Posts

O\'Reilly: Autofilled PHP Forms

Michael Kimsal's Blog: Forget SEO - what about Test Optimization? Debugging and Profiling PHP with Xdebug Installing php-5.2.0 from srpm on CentOS 4

Matthias Noback: Composer "provide" and dependency inversion

Community Events

Don't see your event here?
Let us know!

development unittest release language laravel5 community library opinion interview series laravel psr7 introduction api voicesoftheelephpant framework video extension podcast conference

All content copyright, 2015 :: - Powered by the Solar PHP Framework