Explore >> Select a destination
|
You are here 
|
packagist.org | ||
| | | | |
blog.bitexpert.de
|
|
| | | | | Automate and simplify the process of applying patches to your project files during the Composer install procedure with cweagans/composer-patches and symplify/vendor-patches. | |
| | | | |
ocramius.github.io
|
|
| | | | | A new project that helps you avoid composer packages with known security issues/vulnerabilities | |
| | | | |
blog.packagist.com
|
|
| | | | | Please immediately update Composer to version 2.7.0 or 2.2.23 (composer.phar self-update). The new releases includes fixes for a code execution and possible privilege escalation via InstalledVersions.php or installed.php vulnerability (CVE-2024-24821) reported by Ed Cradock. The vulnerability does not impact packagist.org and Private | |
| | | | |
janikvonrotz.ch
|
|
| | | In web development there are tons of programs and tools and due to that also complex and very different development strategies. Luckily dependency handling got a lot easier. For my Laravel project setup we will use 3 different package managers. Every package manager of course manages a different resource, we will use composer for php packages, npm for everything related to Node.js and Bower for web packages. | ||
