Open Source PHP Package Managers

Composer is a tool for dependency management in PHP, inspired by node's npm and ruby's bundler. It allows you to declare, manage and install the libraries on which your PHP project depends. Unlike most package managers, Composer manages on a per-project basis. It installs packages or libraries in a directory (e.g. vendor) inside your project and does not install anything globally. However, for convenience it does support a "global" project via the global command. Suppose your project depends on a number of libraries which in turn, depend on other libraries. Composer enables you to declare these libraries, finds out which versions of these packages you require, and installs them. You can then update all of your dependencies conveniently with just one command.

AWPS is a modern WordPress starter theme designed for developers who want a streamlined, modular approach to WordPress theme development. It incorporates best practices with a focus on maintainability and performance.

The Dingo API package is meant to provide you, the developer, with a set of tools to help you easily and quickly build your own API. While the goal of this package is to remain as flexible as possible it still won't cover all situations and solve all problems. It is very important to understand which version of Dingo to use, and even more so to understand what is supported and what is not. If the version of dingo you are using is not supported, then please update it, and if necessary your version of Laravel. Much of the package comes preconfigured so that you can start building your API as soon as possible. You can use your .env file to configure most of the package, however, some finer tuning of the package will require you to either publish the configuration file (Laravel) or configure it in bootstrap/app.php (Lumen). You may also use the boot method of your AppServiceProvider.

The composer-asset-plugin is a Composer extension that allows developers to manage frontend dependencies (like npm and Bower packages) through Composer. This bridges the gap between PHP projects and JavaScript/CSS dependencies.

A simple library to encode and decode JSON Web Tokens (JWT) in PHP, conforming to RFC 7519. Use composer to manage your dependencies and download PHP-JWT. Optionally, install the paragonie/sodium_compat package from composer if your php is < 7.2 or does not have libsodium installed. If your private key contains \n characters, be sure to wrap it in double quotes "" and not single quotes '' in order to properly interpret the escaped characters. You must specify supported algorithms for your application. You can add a leeway to account for when there is a clock skew times between the signing and verifying servers. It is recommended that this leeway should not be bigger than a few minutes.

This library aims to provide abstraction for generating various kinds of proxy classes. Available as part of the Tidelift Subscription. The maintainer of ocramius/proxy-manager and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. The suggested installation method is via composer. Build a lazy loadable object with ProxyManager using a Virtual Proxy.

Give thanks (in the form of a GitHub ★ ) to your fellow PHP package maintainers (not limited to Symfony components)! Install this as any other (dev) Composer package. You can also install it once for all your local projects. This will find all of your Composer dependencies, find their Github repository, and star their GitHub repositories. This was inspired by cargo thanks, which was inspired in part by Medium's clapping button as a way to show thanks for someone else's work you've found enjoyment in. If you're wondering why did some dependencies get thanked and not others, the answer is that this plugin only supports Github at the moment. Pull requests are welcome to add support for thanking packages hosted on other services. Package authors can send a star to another package that they would like to thank.

Voyager is a Laravel Admin Package that includes BREAD(CRUD) operations, a media manager, menu builder, and much more. Voyager will take care of your administrative tasks, this way you can focus on what you do best, which is building the next great app! Voyager can save you so much time and it will make building applications even more fun! Baked right in like a fresh loaf of BREAD! Voyager's admin interface allows you to create CRUD or BREAD (Browse, Read, Edit, Add, and Delete) functionality to your posts, pages, or any other table in your database. Voyager has a fully functional media manager which allows you to view/edit/delete files from your storage. All files in your application will be easily accessible and will live in a single place. Compatible with local or s3 file storage. You can easily build menus for your site. In fact the menu in the voyager admin is built using the menu builder. You can add/edit/delete menu items from any menu.

This VM is created for 2 reasons: 1. Very little initial setup work required to Develop / Test / Deploy a Dynamic Web Application live, within minutes. 2. This system should keep running for Years, without requiring Updates / Breakages. If you are new to Virtual Machines, then please watch the Video below ( taken from my other sample PHP project called teamdocs. You may cleanup this Application from the htdocs home folder link & its corresponding database, after logging into mysql. The mysql root login credentials, sample .mysql_history, sample .bash_history are all kept intact for quick references in the home folder. These files can be edited using the free FileZilla ftp client software. This is also explained in the video below. ) Once setup & running, please ensure that a Backup of the system, is taken regularly, to avoid any issues. These are covered in the video. Google Search helps in finding more about PHP development / troubleshooting.

This VM is created for 2 reasons: 1. Very little initial setup work required to Develop / Test / Deploy a Dynamic Web Application live. 2. This system should keep running for Years, without requiring Updates / Breakages. If you are new to Virtual Machines, then please watch the Video below ( taken from my other PHP project called teamdocs. Just replace td with lapp wherever mentioned ) Upload your PHP Files using the free FileZilla ftp client software, to this server called lapp.local and also connect to its postgresql db, using the free pgadmin gui client, from any PC on your LAN. After the application / database is ready, you can access it using https://lapp.local from any LAN PC. Backup the system regularly to avoid any issues. These are covered in the video. Google Search helps in finding more about PHP development / troubleshooting. Apart from Dynamic Applications, you can use this Virtual Machine, to host static webpages too, for the LAN environment.

A simple measure of dependency freshness. Calculates the total number of years behind their respective newest versions for all dependencies listed in composer.json. Run composer global require ecoapm/libyear and make sure your global composer directory is in your $PATH. Alternatively, composer require --dev ecoapm/libyear will add libyear as a local dev dependency for your current directory's app. Download libyear.phar from the latest release, and put it in the current directory, or somewhere in your $PATH to be able to reference it from anywhere. There are obviously more nuanced ways to calculate dependency freshness. The advantage of this approach is its simplicity. You will be able to explain this calculation to your colleagues in about 30s. If your system has two dependencies, the first one year old, the second three, then your system is four libyears out-of-date.