Download the PHP package checkmycomposer/commands without Composer
On this page you can find all versions of the php package checkmycomposer/commands. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download checkmycomposer/commands
More information about checkmycomposer/commands
Files in checkmycomposer/commands
Package commands
Short Description Commands to check your Composer dependencies and synchronize your project with http://checkmycomposer.com.
License MIT
Informations about the package commands
:warning: ABANDONED REPOSITORY. Use https://github.com/fabpot/local-php-security-checker instead.
checkmycomposer-commands
This package provides 2 commands to check your Composer dependencies and synchronize your project with http://checkmycomposer.com.
Getting Started
Follow this link to get started: http://checkmycomposer.com/getting-started
Commands
Check directly your dependencies in your console
To check your dependencies, type the following command in the directory where your composer.json file is stored.
A table will be displayed with all dependencies you are using with several information as in the following image.
Note: You can change the alias of the command ("check") in the "scripts" node of your composer.json file (see section above).
Synchronize your projects with CheckMyComposer
The main interest of CheckMyComposer is to follow your all projects very easily. To complete this, you need to type the following command in the same directory as your composer.json file. Don't forget to store your synchronization token (see section Implementation of token in Getting Started part).
A message will inform you that the synchronization has been succesfully done.
Note: As the checking command, you can change the alias of the command ("synchro") in the "scripts" node of your composer.json file.
Note: We suggest you to synchronize your projects in production environment (this has more interest to follow real versions used by your projects in production). As indicated in Getting Started section, we recommend to store your token in a file (only present in your production server) in this case.
Contributions
Feedback and suggestions are welcome. Feel free to send a pull request!